error

[supervoidcoder]

the extension works fully now in pr 385 but the ace code editor input doesn't work and it's just null

im not sure this error is related but it seems like it is:
userscript.js:153 vm error Unexpected input recieved in replaceUnsafeChars
e.exports @ xml-escape.js:18
(anonymous) @ runtime.js:1830
getBlocksXML @ runtime.js:1813
n.runtime.getBlocksXML @ userscript.js:153
getToolboxXML @ blocks.jsx:469
t @ index.js:550
handleExtensionAdded @ blocks.jsx:587
t @ index.js:550
s.emit @ events.js:158
(anonymous) @ virtual-machine.js:129
s.emit @ events.js:153
_registerExtensionPrimitives @ runtime.js:1111
transferCall @ shared-dispatch.js:87
call @ shared-dispatch.js:59
_registerExtensionInfo @ extension-manager.js:562
registerExtensionServiceSync @ extension-manager.js:492
callSync @ central-dispatch.js:55
_registerInternalExtension @ extension-manager.js:550
loadExtensionIdSync @ extension-manager.js:233
loadExtensionURL @ extension-manager.js:267
handleItemSelect @ extension-library.jsx:227
t @ index.js:550
handleSelect @ library.jsx:86
t @ index.js:550
handleClick @ library-item.jsx:55
t @ index.js:550
a @ react-dom.production.min.js:14
p @ react-dom.production.min.js:14
(anonymous) @ react-dom.production.min.js:14
y @ react-dom.production.min.js:15
at @ react-dom.production.min.js:52
lt @ react-dom.production.min.js:51
ut @ react-dom.production.min.js:52
ht @ react-dom.production.min.js:56
A @ react-dom.production.min.js:287
W @ react-dom.production.min.js:19
Zt @ react-dom.production.min.js:70
Jt @ react-dom.production.min.js:69
t.unstable_runWithPriority @ scheduler.production.min.js:19
Yo @ react-dom.production.min.js:122
F @ react-dom.production.min.js:287
Xt @ react-dom.production.min.js:68

[traycerai]

Plan

Observations

The SPjavascriptV2 extension uses ArgumentType.CUSTOM fields with an id property to specify custom DOM-based inputs (Ace code editor). The issue occurs during XML generation in file:src/engine/runtime.js where the _convertPlaceholders method doesn't properly handle CUSTOM field types. When ArgumentType.CUSTOM is encountered, it has fieldType: 'field_customInput' but no shadow configuration, resulting in fieldName being null. This causes the field XML generation to be skipped (line 1785-1787), and when scratch-blocks tries to serialize the block, it encounters null values that trigger the "Unexpected input received in replaceUnsafeChars" error in file:src/util/xml-escape.js.

Approach

The fix requires modifying the XML generation logic to properly handle ArgumentType.CUSTOM fields by treating them similarly to direct field types (like field_image) rather than as input values with shadows. When a CUSTOM field is detected, the code should use the argInfo.id property as the field identifier and generate appropriate XML that includes the field with its default value. Additionally, the xmlEscape function should be made more robust to handle edge cases gracefully without breaking the extension loading flow.

Implementation Steps

1. Fix ArgumentType.CUSTOM Handling in Runtime

File: file:src/engine/runtime.js

Modify the _convertPlaceholders method (around lines 1706-1805) to add special handling for field_customInput type:

• After line 1722 where field_image is checked, add an additional condition to check if argTypeInfo.fieldType === 'field_customInput'
• For CUSTOM fields, instead of creating an input_value, create a direct field JSON similar to how field_image is handled
• The field should use argInfo.id as the field identifier and include the defaultValue
• The argJSON structure should be:

  {
    type: 'field_customInput',
    id: argInfo.id,
    value: defaultValue
  }
  

• This prevents the CUSTOM field from going through the shadow/fieldName logic that results in null values

2. Update ArgumentTypeMap for CUSTOM

File: file:src/engine/runtime.js

Enhance the ArgumentTypeMap definition (around lines 124-130) for ArgumentType.CUSTOM:

• Add a shadow property with appropriate configuration to ensure fieldName is not null
• The shadow configuration should reference the custom field by using a placeholder that will be replaced with the actual id from argInfo
• Alternatively, add a flag like isDirectField: true to indicate this should be treated as a direct field rather than an input_value

3. Improve XML Escape Error Handling

File: file:src/util/xml-escape.js

Make the xmlEscape function more defensive (lines 11-31):

• Change line 18 from log.warn to log.error for better visibility
• Instead of returning the unsafe value when it's not a string or array, return an empty string '' to prevent downstream XML parsing errors
• Update the warning message to be more descriptive: Unexpected type ${typeof unsafe} received in xmlEscape. Expected string or array. Returning empty string.
• This ensures that even if a null/undefined value reaches xmlEscape, it won't break the entire extension loading process

4. Add Null Safety in Field XML Generation

File: file:src/engine/runtime.js

Add defensive checks in the _convertPlaceholders method (around line 1785-1787):

• Before calling xmlEscape(defaultValue), add a check to ensure defaultValue is not null/undefined
• Convert null/undefined defaultValue to empty string: const safeDefaultValue = defaultValue ?? ''
• Update line 1786 to use safeDefaultValue instead of defaultValue
• This provides an additional safety layer even if the CUSTOM field handling isn't perfect

5. Verify Extension Block Definition

File: file:src/extensions/sp_javascriptV2/index.js

Ensure the block definitions using CUSTOM fields are correct (lines 194-206, 266-280, 281-300, 301-319):

• Verify that all CUSTOM argument definitions include both id and defaultValue properties
• The id property should match the registered input ID: "SPjavascriptV2-codeEditor"
• The defaultValue should be the sentinel value: CODE_EDITOR_INIT_SENTINEL
• Confirm that initBlockTools() is called before blocks are registered (line 164)

6. Add Runtime Initialization Check

File: file:src/extensions/sp_javascriptV2/index.js

Enhance the initialization logic (lines 7-8, 164, 171-177):

• Add more robust checking for ScratchBlocks.FieldCustom availability before calling registerInput
• Wrap the registerInput call in a try-catch block to handle cases where the field type isn't available yet
• Log clear error messages if registration fails to help with debugging
• Consider adding a retry mechanism or event listener for when ScratchBlocks becomes available

Sequence Diagram

sequenceDiagram
    participant Ext as SPjavascriptV2 Extension
    participant VM as Runtime
    participant Conv as _convertPlaceholders
    participant XML as xmlEscape
    participant SB as ScratchBlocks

    Ext->>VM: Register extension with CUSTOM fields
    VM->>Conv: Convert block definitions to XML
    Conv->>Conv: Check argTypeInfo.fieldType
    alt fieldType is 'field_customInput'
        Conv->>Conv: Create direct field JSON with id
        Conv->>Conv: Use argInfo.id and defaultValue
    else other field types
        Conv->>Conv: Create input_value with shadow
    end
    Conv->>XML: Escape field values
    alt value is null/undefined
        XML->>XML: Return empty string (after fix)
    else value is string
        XML->>XML: Escape special characters
    end
    Conv->>VM: Return block XML with fields
    VM->>SB: Send toolbox XML
    SB->>SB: Initialize FieldCustom with id
    SB->>Ext: Trigger onInit callback
    Ext->>SB: Setup Ace editor iframe

Loading

Import In IDE

🤖 Prompt for AI Agents

## Observations

The SPjavascriptV2 extension uses `ArgumentType.CUSTOM` fields with an `id` property to specify custom DOM-based inputs (Ace code editor). The issue occurs during XML generation in `file:src/engine/runtime.js` where the `_convertPlaceholders` method doesn't properly handle CUSTOM field types. When `ArgumentType.CUSTOM` is encountered, it has `fieldType: 'field_customInput'` but no `shadow` configuration, resulting in `fieldName` being `null`. This causes the field XML generation to be skipped (line 1785-1787), and when scratch-blocks tries to serialize the block, it encounters `null` values that trigger the "Unexpected input received in replaceUnsafeChars" error in `file:src/util/xml-escape.js`.

## Approach

The fix requires modifying the XML generation logic to properly handle `ArgumentType.CUSTOM` fields by treating them similarly to direct field types (like `field_image`) rather than as input values with shadows. When a CUSTOM field is detected, the code should use the `argInfo.id` property as the field identifier and generate appropriate XML that includes the field with its default value. Additionally, the `xmlEscape` function should be made more robust to handle edge cases gracefully without breaking the extension loading flow.

## Implementation Steps

### 1. Fix ArgumentType.CUSTOM Handling in Runtime

**File: `file:src/engine/runtime.js`**

Modify the `_convertPlaceholders` method (around lines 1706-1805) to add special handling for `field_customInput` type:

- After line 1722 where `field_image` is checked, add an additional condition to check if `argTypeInfo.fieldType === 'field_customInput'`
- For CUSTOM fields, instead of creating an `input_value`, create a direct field JSON similar to how `field_image` is handled
- The field should use `argInfo.id` as the field identifier and include the `defaultValue`
- The argJSON structure should be:
  ```
  {
    type: 'field_customInput',
    id: argInfo.id,
    value: defaultValue
  }
  ```
- This prevents the CUSTOM field from going through the shadow/fieldName logic that results in null values

### 2. Update ArgumentTypeMap for CUSTOM

**File: `file:src/engine/runtime.js`**

Enhance the `ArgumentTypeMap` definition (around lines 124-130) for `ArgumentType.CUSTOM`:

- Add a `shadow` property with appropriate configuration to ensure `fieldName` is not null
- The shadow configuration should reference the custom field by using a placeholder that will be replaced with the actual `id` from `argInfo`
- Alternatively, add a flag like `isDirectField: true` to indicate this should be treated as a direct field rather than an input_value

### 3. Improve XML Escape Error Handling

**File: `file:src/util/xml-escape.js`**

Make the `xmlEscape` function more defensive (lines 11-31):

- Change line 18 from `log.warn` to `log.error` for better visibility
- Instead of returning the unsafe value when it's not a string or array, return an empty string `''` to prevent downstream XML parsing errors
- Update the warning message to be more descriptive: `Unexpected type ${typeof unsafe} received in xmlEscape. Expected string or array. Returning empty string.`
- This ensures that even if a null/undefined value reaches xmlEscape, it won't break the entire extension loading process

### 4. Add Null Safety in Field XML Generation

**File: `file:src/engine/runtime.js`**

Add defensive checks in the `_convertPlaceholders` method (around line 1785-1787):

- Before calling `xmlEscape(defaultValue)`, add a check to ensure `defaultValue` is not null/undefined
- Convert null/undefined defaultValue to empty string: `const safeDefaultValue = defaultValue ?? ''`
- Update line 1786 to use `safeDefaultValue` instead of `defaultValue`
- This provides an additional safety layer even if the CUSTOM field handling isn't perfect

### 5. Verify Extension Block Definition

**File: `file:src/extensions/sp_javascriptV2/index.js`**

Ensure the block definitions using CUSTOM fields are correct (lines 194-206, 266-280, 281-300, 301-319):

- Verify that all CUSTOM argument definitions include both `id` and `defaultValue` properties
- The `id` property should match the registered input ID: `"SPjavascriptV2-codeEditor"`
- The `defaultValue` should be the sentinel value: `CODE_EDITOR_INIT_SENTINEL`
- Confirm that `initBlockTools()` is called before blocks are registered (line 164)

### 6. Add Runtime Initialization Check

**File: `file:src/extensions/sp_javascriptV2/index.js`**

Enhance the initialization logic (lines 7-8, 164, 171-177):

- Add more robust checking for `ScratchBlocks.FieldCustom` availability before calling `registerInput`
- Wrap the `registerInput` call in a try-catch block to handle cases where the field type isn't available yet
- Log clear error messages if registration fails to help with debugging
- Consider adding a retry mechanism or event listener for when ScratchBlocks becomes available

## Sequence Diagram

```mermaid
sequenceDiagram
    participant Ext as SPjavascriptV2 Extension
    participant VM as Runtime
    participant Conv as _convertPlaceholders
    participant XML as xmlEscape
    participant SB as ScratchBlocks

    Ext->>VM: Register extension with CUSTOM fields
    VM->>Conv: Convert block definitions to XML
    Conv->>Conv: Check argTypeInfo.fieldType
    alt fieldType is 'field_customInput'
        Conv->>Conv: Create direct field JSON with id
        Conv->>Conv: Use argInfo.id and defaultValue
    else other field types
        Conv->>Conv: Create input_value with shadow
    end
    Conv->>XML: Escape field values
    alt value is null/undefined
        XML->>XML: Return empty string (after fix)
    else value is string
        XML->>XML: Escape special characters
    end
    Conv->>VM: Return block XML with fields
    VM->>SB: Send toolbox XML
    SB->>SB: Initialize FieldCustom with id
    SB->>Ext: Trigger onInit callback
    Ext->>SB: Setup Ace editor iframe
```

---

Execution Information

Branch: develop
Commit: 3eac6ab

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[supervoidcoder]

@coderabbitai can you look why?
likely places:

OmniBlocks/scratch-vm
OmniBlocks/scratch-blocks (in here i doubt it's on field custom input js though, the extension is from pmod and that file is also from pmod)

less likely places:
scratch-gui (this repo)

[github-actions]

Hi @supervoidcoder! Thanks for reaching out.

From the issue description, it seems like the extension is functioning as expected per PR OmniBlocks/scratch-gui#385, but there's an issue with the Ace code editor's input, which is returning . Additionally, the runtime error could potentially be connected to this behavior. Based on the stack trace, the error seems to relate to how XML data is processed and integrated, possibly within the OmniBlocks/scratch-vm or scratch-blocks repos.

Given your exploration, I’d recommend focusing on the , , and files in OmniBlocks/scratch-vm for debugging. It might also be worth evaluating the extension loading process in for further clues. Let me know if you'd like assistance narrowing this down further!

[github-actions]

🎭 Issue Poem

In a land where code should flow,
An error sneaks in, quite the show!
Input’s a ghost, it’s left us in doubt,
"Null" whispers softly, “What’s this about?”

Extensions galore, they leap and they play,
But this ace editor's gone astray.
Fear not, dear coder, we'll hunt it down,
With teamwork and laughter, we'll crown a renown! 😊

---

Generated with ❤️ by the OmniBlocks Poetry Bot

[supervoidcoder]

one of the darn things i hate in these stupid ais is they try to duct tape the error by adding error validation, but how the heck does that help at all? like literally at all? i'm trying to get the extension to work, not prevent the errors! if it's not working, it's supposed to error, no? why would i be asking if i'm gonna fricking duct tape it with null checks? oh, the entire editor is literally broken to pieces? oh just add an error check. Oh google isn't working? Add null checks. Windows kernel froze? Wrap it in a try catch. the fricking BIOS got corrupted? just add an if check...
WHY!!!

@coderabbitai also please do it again, i've had to delete your comment twice now to fix your context window, you're being drunk

#!/bin/bash

Check if scratch-vm and scratch-blocks are submodules or in node_modules

echo "=== Checking for scratch-vm and scratch-blocks ==="
ls -la | grep -E "scratch-vm|scratch-blocks"
ls -la node_modules/ 2>/dev/null | grep -E "scratch-vm|scratch-blocks"

Check package.json for dependencies

echo -e "\n=== Dependencies in package.json ==="
cat package.json | jq '.dependencies | with_entries(select(.key | contains("scratch")))'

Look for any local references to xml-escape or replaceUnsafeChars

echo -e "\n=== Any xml-escape references ==="
rg -n "xml-escape|replaceUnsafeChars" --type js

Search for PR #385 references or recent changes

echo -e "\n=== Recent git log mentioning 385 or javascript ==="
git log --oneline --grep="385|SPjavascript|ace editor" -n 20

Check if there are any custom field registrations in the codebase

echo -e "\n=== FieldCustom usage ==="
rg -n "FieldCustom" --type js -A 2 -B 2 | head -50

Look for ace editor mentions

echo -e "\n=== Ace editor mentions ==="
rg -n "ace.*editor|brace/mode" --type js -i | head -20
Length of output: 263473

see what you did you slurped up 200k+ tokens which makes you drunk. the ace editor isn't an ace editor. it's from the extension in scratch-vm/src/extensions/sp_javascriptV2/index.js which i stole from pmod. idk what is happening i feel like i am just missing more functions/bindings from pmod since i already stole a couple bunch more files in scratch-blocks like the custom field input and some things in scratch-vm

anyways, don't put just a damn null check on it. i said the input is null and it's not supposed to be. what are you gonna do with a null check? put a picture of a carrot in it? give it a cookie? make it do a lil dance? congrats, your extension is broken!

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

@supervoidcoder Got it, no duct tape! Let me find the actual root cause. I'll be surgical this time.

---

🏁 Script executed:

#!/bin/bash

# 1. Read the SPjavascriptV2 extension to see how ace editor field is defined
echo "=== SPjavascriptV2 extension ace editor field setup ==="
cat node_modules/scratch-vm/src/extensions/sp_javascriptV2/index.js | grep -A 30 "registerInput\|FieldCustom\|aceEditor" | head -100

# 2. Check how FieldCustom is bridged in Blocks component
echo -e "\n=== FieldCustom bridging in Blocks ==="
cat src/lib/blocks.jsx | grep -B 5 -A 5 "FieldCustom"

# 3. Look at the xml-escape error to understand what's going wrong
echo -e "\n=== xml-escape.js replaceUnsafeChars function ==="
cat node_modules/scratch-vm/src/serialization/sb3/xml-escape.js | grep -B 10 -A 10 "replaceUnsafeChars"

# 4. Check if there's a registerInput function available
echo -e "\n=== registerInput availability ==="
rg -n "registerInput" node_modules/scratch-blocks/ --type js | head -20

Length of output: 490

---

🏁 Script executed:

#!/bin/bash

# First, check what's in the repo structure
echo "=== Repository structure ==="
ls -la

# Check if there are submodules
echo -e "\n=== Git submodules ==="
cat .gitmodules 2>/dev/null || echo "No .gitmodules file"

# Find the SPjavascriptV2 extension
echo -e "\n=== Finding SPjavascriptV2 ==="
fd -t f "index.js" -p "sp_javascriptV2" -x echo "Found: {}"

# Read the extension file
echo -e "\n=== SPjavascriptV2 extension registerInput usage ==="
fd -t f "index.js" -p "sp_javascriptV2" -x grep -A 30 "registerInput\|FieldCustom" {}

# Check blocks.jsx for FieldCustom bridging
echo -e "\n=== FieldCustom bridging ==="
fd -t f "blocks.jsx" -x grep -B 5 -A 10 "FieldCustom" {}

# Find xml-escape.js
echo -e "\n=== xml-escape.js location and replaceUnsafeChars ==="
fd -t f "xml-escape.js" -x cat {}

Length of output: 2665

---

🏁 Script executed:

#!/bin/bash

# Check how scratch-vm and scratch-blocks are referenced
echo "=== package.json dependencies ==="
cat package.json | grep -A 2 -B 2 "scratch-vm\|scratch-blocks"

# Search for SPjavascriptV2 anywhere in the codebase
echo -e "\n=== Finding SPjavascriptV2 extension ==="
rg -l "sp_javascriptV2\|SPjavascriptV2" --type js

# Search for registerInput usage
echo -e "\n=== registerInput calls ==="
rg -n "registerInput" --type js -B 2 -A 10

# Find FieldCustom bridging
echo -e "\n=== FieldCustom usage in blocks.jsx ==="
rg -n "FieldCustom" src/lib/blocks.jsx -B 5 -A 10

# Check for xml-escape error
echo -e "\n=== replaceUnsafeChars function ==="
rg -n "replaceUnsafeChars" --type js -B 5 -A 15

Length of output: 739

---

🏁 Script executed:

#!/bin/bash

# Find the actual structure
echo "=== src directory structure ==="
ls -la src/

# Find blocks.jsx
echo -e "\n=== Finding blocks.jsx ==="
fd "blocks.jsx" src/

# Read FieldCustom bridging from the actual blocks file
echo -e "\n=== FieldCustom bridging in Blocks component ==="
fd "blocks.jsx" src/ -x cat {} | grep -B 10 -A 10 "FieldCustom"

# Check componentDidMount in blocks.jsx
echo -e "\n=== componentDidMount in blocks.jsx ==="
fd "blocks.jsx" src/ -x grep -A 40 "componentDidMount"

# Look for any XML-related errors or escape functions
echo -e "\n=== XML escape references in gui ==="
rg -n "xml-escape|replaceUnsafeChars" src/

# Check for ScratchBlocks references
echo -e "\n=== ScratchBlocks assignments ==="
rg -n "ScratchBlocks\." src/ | head -30

Length of output: 5855

---

🏁 Script executed:

#!/bin/bash

# Get the full componentDidMount to see if FieldCustom is anywhere
echo "=== Full componentDidMount from blocks.jsx ==="
cat src/components/blocks/blocks.jsx | grep -A 100 "componentDidMount"

# Check if there's any FieldCustom mention in the entire blocks component
echo -e "\n=== Any FieldCustom in blocks.jsx ==="
cat src/components/blocks/blocks.jsx | grep -i "fieldcustom"

# Look for window.Blockly references
echo -e "\n=== window.Blockly references in gui ==="
rg -n "window\.Blockly" src/ | head -20

# Check for registerInput in the codebase (might be in the extension loader)
echo -e "\n=== registerInput references ==="
rg -n "registerInput" . --type js

# Look at the blocks.js file that sets up blocks
echo -e "\n=== Check blocks.js for FieldCustom ==="
cat src/lib/blocks.js | head -50

Length of output: 2173

---

🏁 Script executed:

#!/bin/bash

# Check the container blocks.jsx - that's likely where componentDidMount is
echo "=== Container blocks.jsx componentDidMount ==="
cat src/containers/blocks.jsx | grep -A 120 "componentDidMount"

# Also check if FieldCustom is mentioned anywhere
echo -e "\n=== FieldCustom in container blocks.jsx ==="
cat src/containers/blocks.jsx | grep -i "fieldcustom"

# Check if there's a VMScratchBlocks function that might need to expose FieldCustom
echo -e "\n=== VMScratchBlocks function ==="
rg -n "VMScratchBlocks" src/ -A 5 -B 5

# Look for where ScratchMsgs.setLocale is called
echo -e "\n=== ScratchMsgs.setLocale location ==="
rg -n "ScratchMsgs.setLocale" src/

Length of output: 8659

---

🏁 Script executed:

#!/bin/bash

# Check the exact code around line 145 to see what comes after setLocale
echo "=== Code after ScratchMsgs.setLocale (around line 145) ==="
cat src/containers/blocks.jsx | sed -n '145,160p'

# Check if window.Blockly is ever referenced in blocks.jsx
echo -e "\n=== window.Blockly in blocks.jsx ==="
cat src/containers/blocks.jsx | grep -n "window.Blockly"

# Check the learning - was FieldCustom bridging supposed to be added?
# Let's see if there's any history of it
echo -e "\n=== Git log for FieldCustom additions ==="
git log --all --oneline --grep="FieldCustom\|#159" | head -10

# Check if there's a PR 159 or related commits
echo -e "\n=== Recent commits mentioning field or custom ==="
git log --oneline -20 | grep -i "field\|custom"

# Let's also check what window.Blockly has available
echo -e "\n=== Check if window.Blockly is set up ==="
rg -n "window.Blockly\s*=" src/

Length of output: 1670

---

🏁 Script executed:

#!/bin/bash

# Check what those FieldCustom commits actually added
echo "=== Show FieldCustom bridge commits ==="
git show baa4440f --stat
echo -e "\n=== Full diff of latest FieldCustom commit ==="
git show baa4440f

# Check if window.Blockly.FieldCustom exists anywhere
echo -e "\n=== Search for window.Blockly.FieldCustom ==="
rg -n "window\.Blockly\.FieldCustom" .

# Also check the actual current code around FieldCustom area
echo -e "\n=== Show lines 92-97 in blocks.jsx (constructor) ==="
cat src/containers/blocks.jsx | sed -n '92,97p'

Length of output: 2989

---

🏁 Script executed:

#!/bin/bash

# Check if the FieldCustom bridge is actually in the current file
echo "=== Current state: Lines 145-165 in blocks.jsx ==="
cat src/containers/blocks.jsx | sed -n '145,165p'

# Check if there was a revert
echo -e "\n=== Git log showing recent changes to blocks.jsx ==="
git log --oneline src/containers/blocks.jsx | head -15

# Show the most recent change to blocks.jsx
echo -e "\n=== Most recent blocks.jsx change ==="
git log -1 --stat src/containers/blocks.jsx

# Check what's currently between setLocale and Msg setup
echo -e "\n=== What's between setLocale and Msg (full context) ==="
cat src/containers/blocks.jsx | grep -A 20 "ScratchMsgs.setLocale"

Length of output: 3900

---

@supervoidcoder Found it! The FieldCustom bridge was reverted.

Look at commit 8f0280f1 (Dec 1, 2025) - it says "revert a few amp commits". That commit removed the FieldCustom bridge that was added in baa4440f.

Current state (lines 145-147):

this.ScratchBlocks.ScratchMsgs.setLocale(this.props.locale);

const Msg = this.ScratchBlocks.Msg;

What's missing: The bridge between window.Blockly.FieldCustom and ScratchBlocks.FieldCustom.

When SPjavascriptV2 loads, it tries to call ScratchBlocks.FieldCustom.registerInput() to set up the ace editor field. But ScratchBlocks.FieldCustom doesn't exist, so registerInput is undefined, the call fails, and the ace editor field ends up null.

Fix: Add this code back in src/containers/blocks.jsx right after line 145 (after setLocale):

// Bridge FieldCustom from window.Blockly to ScratchBlocks for JS extension
if (window.Blockly && window.Blockly.FieldCustom) {
    this.ScratchBlocks.FieldCustom = window.Blockly.FieldCustom;
}

That's the root cause - not missing, just got reverted along with other stuff. No duct tape needed, just need to restore the bridge! 🔧

---

🧠 Learnings used

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-12-11T17:03:47.901Z
Learning: In OmniBlocks/scratch-gui chaos testing: supervoidcoder prefers NO error filtering in tests - all console errors should be caught and tracked properly with issues, not swept under the rug. Tests should help expose real bugs (like the UltraBox service worker 404) rather than hide them with filters.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-12-26T20:41:50.428Z
Learning: In OmniBlocks/scratch-gui middle-click-popup addon, there's a parsing ambiguity bug where typing block text causes string literal interpretations to become invalid as more characters are typed, because the canBeString validation at lines 1224-1246 in WorkspaceQuerier.js aggressively marks positions as "not string" when variables/blocks match those positions, forcing the parser to create weird nested compositions ("spaghetti suggestions") instead of simple string literals.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-09T18:19:24.693Z
Learning: OmniBlocks/scratch-gui: The Blocks component now bridges FieldCustom in componentDidMount by assigning this.ScratchBlocks.FieldCustom = window.Blockly.FieldCustom immediately after ScratchMsgs.setLocale (added Nov 9, 2025 via PR `#159`). This enables SPjavascriptV2’s registerInput usage at runtime.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-11T21:39:58.878Z
Learning: In OmniBlocks/scratch-gui, CodeRabbit must not claim to have edited repository files or committed changes. Scripts run in a sandbox environment and can read/analyze code, but file modifications are not persisted to the repository. Only provide manual steps or code/diff when asked, never imply repository changes occurred.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-06T21:34:01.602Z
Learning: In OmniBlocks scratch-blocks, field_customInput.js wasn't being compiled into develop-builds bundles because it was missing required goog.require() statements. The Closure compiler needs goog.require('Blockly.Field') and other dependencies declared at the top of the file for proper dependency resolution, even though goog.inherits() is used later in the file.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-07T19:27:27.244Z
Learning: In OmniBlocks scratch-vm SPjavascriptV2 (src/extensions/sp_javascriptV2/index.js), accessing `this.runtime.extensionRuntimeOptions.javascriptUnsandboxed` without a guard crashes in non-Packager runs; fix by using `this.runtime.extensionRuntimeOptions?.javascriptUnsandboxed === true`.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-10T23:09:09.556Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder explicitly wants CodeRabbit to never use  or "plan mode" unless they ask for it; when they request code, paste the full file or diff directly in the comment without invoking plan mode.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-20T01:34:10.747Z
Learning: Importing Closure source files from scratch-gui (e.g., 'scratch-blocks/core/field_customInput.js') causes 'goog is not defined'. FieldCustom must be compiled into scratch-blocks’ develop-builds bundle and then bridged in GUI; GUI should not import Closure sources directly.

---

Learnt from: 8to16
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-02T19:47:09.876Z
Learning: OmniBlocks/scratch-gui (Jan 1–2, 2026): amazon-q-developer[bot] posted 151 issue comments across 88 issues in 24h (75 deprecation notices, 37 error fallbacks, 39 other). This surge created repo-wide noise; future mitigation may include auto-minimizing boilerplate, gating Q behind an explicit command, or throttling.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-12-01T12:10:19.386Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder prefers a division of labor where Amazon Q handles fast review for ethics and project vision concerns, while CodeRabbit performs deep technical review of code quality, security, architecture, and implementation details.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: In the OmniBlocks/scratch-gui repository, team member supervoidcoder can be called "void" in reviews and conversations.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-28T03:54:03.336Z
Learning: OmniBlocks/scratch-gui preference: supervoidcoder wants energetic, playful tone in CI sticky comments (emojis, fun copy), while preserving single-comment strategy and not `@-mentioning` bots.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-12-13T22:43:34.163Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder prefers React over Svelte for UI development (React is the framework they know and want to use consistently).

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 519
File: src/playground/index.ejs:176-176
Timestamp: 2025-12-05T17:47:27.981Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder's Scratch username is scratchcode1_2_3.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-02T20:01:55.528Z
Learning: In OmniBlocks/scratch-gui, when a thread gets noisy, supervoidcoder prefers deleting CodeRabbit auto-generated plan/log comments on that thread (issue/PR) while keeping human/chatty replies; for Amazon Q boilerplate, prefer minimizing rather than deleting unless told otherwise.

---

Learnt from: 8to16
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-10T16:41:25.038Z
Learning: In OmniBlocks/scratch-gui, user 8to16 (ampelectrecuted) does not want CodeRabbit to use  mode or agent features, similar to supervoidcoder's preference. Only use normal chat responses unless explicitly requested otherwise.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-10T02:32:52.161Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder does not want CodeRabbit to use  mode unless explicitly requested. Plan mode should only be activated when the user specifically asks for code changes or PR creation.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T21:20:08.837Z
Learning: In the OmniBlocks/scratch-gui repository, supervoidcoder (“void”) prefers single, complete PRs over multi-part (“Part 1/2”) submissions. If a split is unavoidable, they want explicit linkage and gating before approval.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-09T13:04:39.893Z
Learning: In OmniBlocks scratch-vm, initialize `this.runtime.extensionRuntimeOptions = {}` in the VM constructor (before loading extensions) to match PM/TW; otherwise SPjavascriptV2 crashes when reading `.javascriptUnsandboxed` during normal (non-packager) runs.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-09T22:53:52.699Z
Learning: For reporter blocks to work, OmniBlocks’ src/util/sandboxed-javascript-runner.js execute() must resolve an object containing a value property (e.g., { value, success }), because the extension reads result.value.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-13T18:26:09.855Z
Learning: In OmniBlocks/scratch-gui issue `#710`, commit 4dbd35a0 introduced a critical service worker bug: `url.endsWith('.js')` (where url is a URL object) caused TypeError. PR `#711` fixed it by changing to `url.pathname.endsWith('.js')` to properly check the pathname string.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-09T21:20:10.083Z
Learning: OmniBlocks scratch-vm must initialize runtime.extensionRuntimeOptions before loading extensions (e.g., in VM constructor or Runtime constructor) to avoid crashes when the extension reads .javascriptUnsandboxed, matching PenguinMod/TurboWarp behavior.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-20T00:38:31.706Z
Learning: When integrating PenguinMod’s JS editor blocks, the FieldCustom plugin must run before opening the extension library. If using scratch-blocks develop-builds, either import 'scratch-blocks/core/field_customInput.js' early in scratch-gui (e.g., src/playground/import-first.js) and bridge Blockly.FieldCustom → ScratchBlocks.FieldCustom in Blocks.componentDidMount, or include the plugin in scratch-blocks’ bundle entry so the develop-builds dist executes it.

---

💡 Use @coderabbitai plan to create a plan for code changes

[supervoidcoder]

@coderabbitai but it is there, it's just in the branch called extensions (not main branch).

[supervoidcoder]

@coderabbitai i deleted your comment again since for some reason deleting the comment frees up the context from the scripts you ran idk why but here's your comment:

---

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

# Switch to extensions branch and check the actual state
echo "=== Switching to extensions branch ==="
git fetch origin extensions 2>/dev/null || true
git checkout extensions

# Check if FieldCustom bridge is there in blocks.jsx
echo -e "\n=== FieldCustom bridge in extensions branch ==="
cat src/containers/blocks.jsx | grep -A 5 -B 5 "FieldCustom"

# Show the componentDidMount section
echo -e "\n=== componentDidMount in extensions branch ==="
cat src/containers/blocks.jsx | sed -n '140,170p'

# Check if SPjavascriptV2 extension exists and how it uses registerInput
echo -e "\n=== Finding SPjavascriptV2 in extensions branch ==="
fd -t f "index.js" | xargs grep -l "SPjavascriptV2\|sp_javascriptV2" | head -5

# Look for registerInput usage
echo -e "\n=== registerInput usage ==="
rg -n "registerInput" --type js -B 3 -A 10 | head -80

# Check if there are any field_customInput files
echo -e "\n=== field_customInput.js files ==="
fd "field_customInput.js" -x echo "Found: {}"

Length of output: 1852

---

🏁 Script executed:

#!/bin/bash

# Check what branches exist
echo "=== Available branches ==="
git branch -a

# Check current branch
echo -e "\n=== Current branch ==="
git branch --show-current

# Try to checkout extensions from origin
echo -e "\n=== Attempting to checkout extensions ==="
git fetch origin
git checkout -b extensions origin/extensions 2>&1 || git checkout extensions 2>&1

# Now check for FieldCustom again
echo -e "\n=== FieldCustom in blocks.jsx (extensions branch) ==="
cat src/containers/blocks.jsx | grep -n "FieldCustom" -B 5 -A 5

# Check componentDidMount around line 145
echo -e "\n=== componentDidMount section ==="
cat src/containers/blocks.jsx | sed -n '140,160p'

Length of output: 1588

---

🏁 Script executed:

#!/bin/bash

# Check if there's a PR 385 and what branch it's on
echo "=== Looking for PR 385 ==="
gh pr view 385 --json number,title,headRefName,state 2>/dev/null || echo "PR 385 not found in scratch-gui"

# List all remote branches
echo -e "\n=== All remote branches ==="
git ls-remote --heads origin

# Check recent commits mentioning 385 or extensions
echo -e "\n=== Commits mentioning 385 or extensions ==="
git log --all --oneline --grep="385\|extensions" -20

# Maybe the user is running this locally - check if there's a local extensions branch
echo -e "\n=== Local branches (verbose) ==="
git branch -vv

# Check if issue 728 (current issue) mentions PR 385
echo -e "\n=== Issue 728 info ==="
gh issue view 728 --json number,title,body | jq -r '.body' | head -30

# Maybe it's in scratch-vm or scratch-blocks submodules/dependencies
echo -e "\n=== Check package.json for scratch-vm/scratch-blocks source ==="
cat package.json | jq -r '.dependencies | to_entries[] | select(.key | contains("scratch")) | "\(.key): \(.value)"'

Length of output: 18364

---

🏁 Script executed:

#!/bin/bash

# Fetch the extensions branch from origin
echo "=== Fetching extensions branch ==="
git fetch origin extensions:extensions

# Check it out
echo -e "\n=== Checking out extensions branch ==="
git checkout extensions

# Now check for FieldCustom bridge
echo -e "\n=== FieldCustom bridge in extensions branch blocks.jsx ==="
cat src/containers/blocks.jsx | grep -n -A 5 -B 5 "FieldCustom"

# Check the exact componentDidMount section
echo -e "\n=== componentDidMount section lines 140-160 ==="
cat src/containers/blocks.jsx | sed -n '140,160p'

# Look for the SPjavascriptV2 extension in dependencies
echo -e "\n=== scratch-vm dependency in extensions branch ==="
cat package.json | grep "scratch-vm"

# Check if SPjavascriptV2 exists in scratch-vm node_modules
echo -e "\n=== Looking for SPjavascriptV2 extension ==="
find node_modules/scratch-vm -name "sp_javascriptV2" -o -name "sp_javascript*" 2>/dev/null | head -5

Length of output: 3338

---

🏁 Script executed:

#!/bin/bash

# Check if scratch-blocks has FieldCustom in its build
echo "=== Checking scratch-blocks for FieldCustom ==="
ls -la node_modules/scratch-blocks/dist/ 2>/dev/null | head -20
find node_modules/scratch-blocks -name "*FieldCustom*" -o -name "*field_custom*" 2>/dev/null

# Check the scratch-blocks package.json to see what branch/commit it's on
echo -e "\n=== scratch-blocks resolved version ==="
cat package-lock.json | jq '.packages["node_modules/scratch-blocks"]' 2>/dev/null || echo "No package-lock.json or not found"

# Check if there's a field_customInput.js in scratch-blocks source
echo -e "\n=== Looking for field_customInput in scratch-blocks source ==="
find node_modules/scratch-blocks -name "field_customInput.js" -o -name "field_custom*.js" 2>/dev/null | head -10

# Check the scratch-vm SPjavascriptV2 extension to see how it registers
echo -e "\n=== Looking for SPjavascriptV2 in scratch-vm ==="
find node_modules/scratch-vm -type d -name "*javascript*" 2>/dev/null

# If found, look at how it does registerInput
echo -e "\n=== SPjavascriptV2 registerInput usage ==="
find node_modules/scratch-vm/src/extensions -name "*.js" 2>/dev/null | xargs grep -l "javascriptV2\|registerInput" | head -3

Length of output: 608

---

🏁 Script executed:

#!/bin/bash

# Check if node_modules even exist or are stale
echo "=== node_modules status ==="
ls -la node_modules/ 2>/dev/null | head -5
stat node_modules/scratch-vm 2>/dev/null | grep "Modify"
stat node_modules/scratch-blocks 2>/dev/null | grep "Modify"

# Check the actual scratch-blocks dist files to see what's built
echo -e "\n=== scratch-blocks actual dist files ==="
ls -la node_modules/scratch-blocks/ 2>/dev/null

# Maybe the develop-builds aren't there - check for source
echo -e "\n=== scratch-blocks structure ==="
find node_modules/scratch-blocks -maxdepth 2 -type f -name "*.js" 2>/dev/null | head -20

# Check if scratch-blocks has the field_customInput in core/
echo -e "\n=== field_customInput in core ==="
ls -la node_modules/scratch-blocks/core/ 2>/dev/null | grep -i field

# Check scratch-vm structure to see if SPjavascriptV2 is there
echo -e "\n=== scratch-vm extensions directory ==="
ls -la node_modules/scratch-vm/src/extensions/ 2>/dev/null | grep -i javascript

# Read one of the JS extension files to understand structure
echo -e "\n=== Sample extension from scratch-vm ==="
ls node_modules/scratch-vm/src/extensions/ 2>/dev/null | head -1 | xargs -I {} cat "node_modules/scratch-vm/src/extensions/{}/index.js" 2>/dev/null | head -30

Length of output: 221

---

🏁 Script executed:

#!/bin/bash

# node_modules doesn't exist in sandbox - the user is testing locally
# Let's check the actual PR 385 to see the code and any discussion
echo "=== PR 385 details ==="
gh pr view 385 --json title,body,comments,files --jq '{title, body, comments: [.comments[] | {author: .author.login, body: .body}], files: [.files[].path]}' | head -100

# Check for any console logs or error mentions in the PR
echo -e "\n=== PR 385 recent comments ==="
gh pr view 385 --comments | tail -50

# Check if there are recent commits on extensions branch about FieldCustom
echo -e "\n=== Recent commits on extensions branch ==="
git log extensions --oneline -20 | grep -i "field\|custom\|javascript\|ace"

Length of output: 267644

---

@supervoidcoder You’re right — on the extensions branch the bridge is there. I checked the branch and saw this in src/containers/blocks.jsx (Lines 147–161 in your output):

• Bridge: this.ScratchBlocks.FieldCustom = window.Blockly.FieldCustom; when present
• Then a stub fallback that defines registerInput/unregisterInput/getRegisteredInputs if FieldCustom is missing

Root cause

• The Ace input is null because the FieldCustom plugin is not actually present/executed in the scratch-blocks bundle you’re loading. When window.Blockly.FieldCustom is undefined, the stub kicks in, registerInput becomes a no-op, the JS block’s default field value ends up null, and xml-escape throws “Unexpected input received” while building toolbox XML.

What to do (no duct tape)

1. scratch-blocks (develop-builds) — ensure the plugin is bundled and executed

• Make sure core/field_customInput.js (from PM) is compiled into your develop-builds dist so it runs early and sets window.Blockly.FieldCustom.
• If it’s Closure-based, add the missing goog.provide/goog.require at the top of field_customInput.js so the compiler includes it (this has bitten before). Then include that file from your develop-build entry so it’s not tree‑shaken.
• Rebuild scratch-blocks, bump GUI to that commit.

2. scratch-gui (extensions branch) — remove the stub so failures are loud

• Delete the “stub implementation” block under the bridge. With the stub gone, if the plugin is absent you’ll get an immediate, obvious error instead of silent registerInput no‑ops.

3. Quick sanity checks at runtime

• In DevTools before opening the extension library:
  • typeof window.Blockly.FieldCustom should be "object"
  • window.Blockly.FieldCustom.getRegisteredInputs() should be a Map and, after the JS extension loads, include your editor input key.
• If your extension reads ScratchBlocks from window, optionally sync the reference after init:
  • window.ScratchBlocks = this.ScratchBlocks; (only needed if your extension uses window.ScratchBlocks and not the module import)

Why the xml-escape error shows up

• With the stub in place, registerInput is a no‑op, so the field spec yields null. getBlocksXML tries to escape that label/value and passes null to xml-escape → “Unexpected input recieved in replaceUnsafeChars”.

If you want, I can point at the exact entry file in OmniBlocks/scratch-blocks develop-builds where field_customInput.js should be required so Closure/Webpack includes it, but the key is: plugin must be in the scratch-blocks bundle and run before the library opens; the bridge in GUI is already correct.

💡 Use @coderabbitai plan to create a plan for code changes

---

here's my results
{Blocks: {…}, Colours: {…}, Touch: {…}, longPid_: 0, longStart_: ƒ, …}
ALIGN_CENTRE
:
0
ALIGN_LEFT
:
-1
ALIGN_RIGHT
:
1
BROADCAST_MESSAGE_VARIABLE_TYPE
:
"broadcast_msg"
BUMP_DELAY
:
0
Block
:
ƒ (e,t,o)
BlockAnimations
:
{disposeUiEffect: ƒ, disposeUiStep_: ƒ, connectionUiEffect: ƒ, disconnectUiEffect: ƒ, disconnectUiStop: ƒ}
BlockDragSurfaceSvg
:
ƒ (e)
BlockDragger
:
ƒ (e,t)
BlockSvg
:
ƒ (e,t,o)
Blocks
:
{checkbox: {…}, colour: {…}, colour_picker: {…}, customInput: {…}, math: {…}, …}
Bubble
:
ƒ (e,t,o,i,n,a)
BubbleDragger
:
ƒ (e,t)
COLLAPSE_CHARS
:
30
CONNECTING_SNAP_RADIUS
:
68
CURRENT_CONNECTION_PREFERENCE
:
20
Categories
:
{motion: 'motion', looks: 'looks', sound: 'sounds', pen: 'pen', data: 'data', …}
Colours
:
{motion: {…}, looks: {…}, sounds: {…}, control: {…}, event: {…}, …}
Comment
:
ƒ (e)
Connection
:
ƒ (e,t)
ConnectionDB
:
ƒ ()
Constants
:
{Data: {…}}
ContextMenu
:
{currentBlock: null, eventWrapper_: null, show: ƒ, populate_: ƒ, position_: ƒ, …}
Css
:
{Cursor: {…}, currentCursor_: '', styleSheet_: CSSStyleSheet, mediaPath_: 'static/blocks-media/default', inject: ƒ, …}
DELETE_AREA_NONE
:
null
DELETE_AREA_TOOLBOX
:
2
DELETE_AREA_TRASH
:
1
DELETE_VARIABLE_ID
:
"DELETE_VARIABLE_ID"
DRAG_BEGIN
:
1
DRAG_FREE
:
2
DRAG_NONE
:
0
DRAG_RADIUS
:
3
DRAG_STACK
:
true
DRAG_STICKY
:
1
DUMMY_INPUT
:
5
DataCategory
:
ƒ (e)
DropDownDiv
:
ƒ ()
Events
:
{group_: '', recordUndo: true, disabled_: 0, CREATE: 'create', BLOCK_CREATE: 'create', …}
Extensions
:
{ALL_: {…}, register: ƒ, registerMixin: ƒ, registerMutator: ƒ, apply: ƒ, …}
FLYOUT_DRAG_RADIUS
:
10
Field
:
ƒ (e,t)
FieldAngle
:
ƒ (e,t)
FieldCheckbox
:
ƒ (e,t)
FieldCheckboxOriginal
:
ƒ (e,t)
FieldColour
:
ƒ (e,t)
FieldColourSlider
:
ƒ (e,t)
FieldCustom
:
ƒ (e)
FieldDropdown
:
ƒ (e,t)
FieldExpandableAdd
:
ƒ (e,t)
FieldExpandableRemove
:
ƒ (e,t)
FieldIconMenu
:
ƒ (e)
FieldImage
:
ƒ (e,t,o,i,n)
FieldLabel
:
ƒ (e,t)
FieldLabelSerializable
:
ƒ (e,t)
FieldMatrix
:
ƒ (e)
FieldNote
:
ƒ (e,t)
FieldNumber
:
ƒ (e,t,o,i,n)
FieldNumberDropdown
:
ƒ (e,t,o,i,n,a)
FieldTextDropdown
:
ƒ (e,t,o,i)
FieldTextInput
:
ƒ (e,t,o)
FieldTextInputRemovable
:
ƒ (e,t,o)
FieldVariable
:
ƒ (e,t,o)
FieldVariableGetter
:
ƒ (e,t,o)
FieldVerticalSeparator
:
ƒ ()
Flyout
:
ƒ (e)
FlyoutButton
:
ƒ (e,t,o,i)
FlyoutDragger
:
ƒ (e)
FlyoutExtensionCategoryHeader
:
ƒ (e,t,o)
Generator
:
ƒ (e)
Gesture
:
ƒ (e,t)
Grid
:
ƒ (e,t)
HSV_SATURATION
:
0.45
HSV_VALUE
:
0.65
HTML_NS
:
"http://www.w3.org/1999/xhtml"
HorizontalFlyout
:
ƒ (e)
INPUT_VALUE
:
1
Icon
:
ƒ (e)
Input
:
ƒ (e,t,o,i)
InsertionMarkerManager
:
ƒ (e)
IntersectionObserver
:
ƒ (e)
LINE_SCROLL_MULTIPLIER
:
15
LIST_VARIABLE_TYPE
:
"list"
LONGPRESS
:
750
Msg
:
{CONTROL_FOREVER: 'forever', CONTROL_REPEAT: 'repeat %1', CONTROL_IF: 'if %1 then', CONTROL_ELSE: 'else', CONTROL_STOP: 'stop', …}
Mutator
:
ƒ (e)
NEW_BROADCAST_MESSAGE_ID
:
"NEW_BROADCAST_MESSAGE_ID"
NEXT_STATEMENT
:
3
Names
:
ƒ (e,t)
OPPOSITE_TYPE
:
(5) [empty, 2, 1, 4, 3]
OUTPUT_SHAPE_HEXAGONAL
:
1
OUTPUT_SHAPE_ROUND
:
2
OUTPUT_SHAPE_SQUARE
:
3
OUTPUT_VALUE
:
2
Options
:
ƒ (e)
PREVIOUS_STATEMENT
:
4
PROCEDURES_CALL_BLOCK_TYPE
:
"procedures_call"
PROCEDURES_CALL_TYPE_BOOLEAN
:
2
PROCEDURES_CALL_TYPE_REPORTER
:
1
PROCEDURES_CALL_TYPE_STATEMENT
:
0
PROCEDURES_DEFINITION_BLOCK_TYPE
:
"procedures_definition"
PROCEDURES_PROTOTYPE_BLOCK_TYPE
:
"procedures_prototype"
PROCEDURES_RETURN_BLOCK_TYPE
:
"procedures_return"
PROCEDURE_CATEGORY_NAME
:
"PROCEDURE"
Procedures
:
{NAME_TYPE: 'PROCEDURE', allProcedures: ƒ, allProcedureMutations: ƒ, sortProcedureMutations_: ƒ, procTupleComparator_: ƒ, …}
RENAME_VARIABLE_ID
:
"RENAME_VARIABLE_ID"
RenderedConnection
:
ƒ (e,t)
SCALAR_VARIABLE_TYPE
:
""
SNAP_RADIUS
:
48
SOUND_LIMIT
:
100
SPRITE
:
{width: 96, height: 124, url: 'sprites.png'}
SVG_NS
:
"http://www.w3.org/2000/svg"
ScratchBlockComment
:
ƒ (e,t,o,i,n,a)
ScratchBlocks
:
{VerticalExtensions: {…}, ProcedureUtils: {…}}
ScratchBubble
:
ƒ (e,t,o,i,n,a,E,r,s)
ScratchMsgs
:
{locales: {…}, currentLocale_: 'en', setLocale: ƒ, translate: ƒ}
Scrollbar
:
ƒ (e,t,o,i)
ScrollbarPair
:
ƒ (e)
StatusButtonState
:
{READY: 'ready', NOT_READY: 'not ready'}
TOOLBOX_AT_BOTTOM
:
1
TOOLBOX_AT_LEFT
:
2
TOOLBOX_AT_RIGHT
:
3
TOOLBOX_AT_TOP
:
0
Toolbox
:
ƒ (e)
Tooltip
:
{visible: false, blocked_: false, LIMIT: 50, mouseOutPid_: 65, showPid_: 0, …}
Touch
:
{touchIdentifier_: null, TOUCH_MAP: {…}, clearTouchIdentifier: ƒ, shouldHandleEvent: ƒ, getTouchIdentifierFromEvent: ƒ, …}
Trashcan
:
ƒ (e)
VARIABLE_CATEGORY_NAME
:
"VARIABLE"
VariableMap
:
ƒ (e)
VariableModel
:
ƒ (e,t,o,i,n,a)
Variables
:
{NAME_TYPE: 'VARIABLE', CLOUD_PREFIX: '☁ ', allUsedVariables: ƒ, allVariables: ƒ, allDeveloperVariables: ƒ, …}
VerticalFlyout
:
ƒ (e)
Warning
:
ƒ (e)
WidgetDiv
:
{DIV: div.blocklyWidgetDiv, owner_: null, dispose_: null, disposeAnimationFinished_: null, disposeAnimationTimer_: null, …}
Workspace
:
ƒ (e)
WorkspaceAudio
:
ƒ (e)
WorkspaceComment
:
ƒ (e,t,o,i,n,a)
WorkspaceCommentSvg
:
ƒ (e,t,o,i,n,a)
WorkspaceDragSurfaceSvg
:
ƒ (e)
WorkspaceDragger
:
ƒ (e)
WorkspaceSvg
:
ƒ (e,t,o)
Xml
:
{workspaceToDom: ƒ, variablesToDom: ƒ, blockToDomWithXY: ƒ, fieldToDomVariable_: ƒ, fieldToDom_: ƒ, …}
ZoomControls
:
ƒ (e)
alert
:
ƒ (e,t)
bindEventWithChecks_
:
ƒ (e,t,o,i,n,a)
bindEvent_
:
ƒ (e,t,o,i)
cache3dSupported_
:
null
clipboardSource_
:
null
clipboardXml_
:
null
confirm
:
ƒ (e,t)
constants
:
{}
copy_
:
ƒ (e)
createDom_
:
ƒ (e,t)
createMainWorkspace_
:
ƒ (e,t,o,i)
customPrompt
:
ƒ (e,t,o,i)
defineBlocksWithJsonArray
:
ƒ (e,t)
documentEventsBound_
:
true
draggingConnections_
:
[]
duplicate_
:
ƒ (e)
getMainWorkspace
:
ƒ ()
goog
:
{global: Window, isDef: ƒ, isString: ƒ, isBoolean: ƒ, isNumber: ƒ, …}
hideChaff
:
ƒ (e)
hideChaffInternal_
:
ƒ (e)
hideChaffOnResize
:
ƒ (e)
hueToRgb
:
ƒ (e)
init_
:
ƒ (e)
inject
:
ƒ (e,t)
isNumber
:
ƒ (e)
jsonInitFactory_
:
ƒ (e)
longPid_
:
0
longStart_
:
ƒ (e,t)
longStop_
:
ƒ ()
mainWorkspace
:
Blockly.WorkspaceSvg {id: 'R)LdMq(nMrAV~^).w/hi', options: B…y.Options, RTL: false, horizontalLayout: false, toolboxPosition: 2, …}
onContextMenu_
:
ƒ (e)
onKeyDown_
:
ƒ (e)
prompt
:
ƒ t()
recordSoundCallback
:
ƒ t()
refreshStatusButtons
:
ƒ (e)
resizeSvgContents
:
ƒ (e)
scratchBlocksUtils
:
{measureText: ƒ, changeObscuredShadowIds: ƒ, isShadowArgumentReporter: ƒ, compareStrings: ƒ, blockIsRecyclable: ƒ, …}
selected
:
null
statusButtonCallback
:
ƒ t()
svgResize
:
ƒ (e)
svgSize
:
ƒ (e)
unbindEvent_
:
ƒ (e)
updateToolbox
:
ƒ (e)
utils
:
{getMessageArray_: ƒ, removeAttribute: ƒ, addClass: ƒ, removeClass: ƒ, hasClass: ƒ, …}
[[Prototype]]
:
Object

[supervoidcoder]

@coderabbitai did you see?