[examples/images] Cmd+A selects image void nodes instead of editor text

[wudidewo12]

Description

In the Images example, pressing Cmd+A after focusing the editor does not select the editor text on the local v2 build. Instead, the image/void nodes show blue selection lines and delete icons.

The live Slate examples page selects the editor body content with the same operation.

Recording

Screenshots attached below:

Local actual behavior:

Live reference expected behavior:

Video attached below:

• Local actual behavior: after pressing Cmd+A, only the image/void nodes show selected state and delete icons.
• Live reference behavior: after pressing Cmd+A, the editor body text is selected.

Sandbox

No response.

Local reproduction URL:

http://localhost:3100/examples/images

Live reference URL:

https://www.slatejs.org/examples/images

Steps

To reproduce the behavior:

1. Open http://localhost:3100/examples/images.
2. Click inside the editor text so the Images editor has focus.
3. Press Cmd+A once.
4. Compare with https://www.slatejs.org/examples/images using the same steps.

Expectation

The local v2 build should match the live Slate example. Pressing Cmd+A should select the editor body content.

Actual behavior

On the local v2 build, the editor text is not selected. Instead, the image/void nodes show blue selection lines and delete icons.

Environment

• OS: macOS
• Branch: v2
• Commit: ce2bd6c6
• Install/run method: local repo with bun serve
• Affected example: /examples/images

Impact

The select-all keyboard shortcut behaves inconsistently in the Images example. This makes keyboard editing confusing around image/void nodes and does not match the live reference behavior.

[wudidewo12]

Additional note:

After the incorrect Cmd+A selection state, typing a character can also replace the editor content unexpectedly. In my local retest, pressing Cmd+A in the Images editor and then typing a left only a in the editor.

This seems likely related to the same selection-scope issue rather than a separate bug.

[zbeyens]

🟢 95-100% confidence

Phase	🧪 Tests	🌐 Browser
Reproduced	🔴 Images select-all row failed in the issue plan	✅ Local behavior matched the report
Verified	🟢 Focused images row passed	✅ Editor text selected; image chrome no longer shows direct selected state

🌐 Browser Check

• Open http://localhost:3100/examples/images.
• Click inside the editor text.
• Press Cmd+A once.
• Confirm the editor body text selection is active and image voids do not show direct selected chrome/delete controls.

✅ Outcome

• Cmd+A from text focus selects the editor body content.
• Image void selection chrome no longer appears for that broad text selection.

⚠️ Caveat

• Report baseline was ce2bd6c6; current v2 HEAD 07d79634 contains the verified behavior.

🏗️ Design

• Chosen owner: image example direct-selection chrome.
• Why not quick patch: the model select-all path already selected editor text; forcing the keyboard path would patch the wrong layer.
• Why not broader change: this did not need a global void-selection contract change.

🧪 Verified

• PLAYWRIGHT_RETRIES=0 PLAYWRIGHT_BASE_URL=http://localhost:3100 bun playwright playwright/integration/examples/images.test.ts --project=chromium --grep "copies selected image with visible external HTML payload|selects image editor text content from text focus with keyboard select all"
• bun check

[zbeyens]

Closing: current v2 HEAD is verified with 95%+ confidence.