Android/iOS Enter·Backspace block boundary 실기기 trace 수집

[developer-1px]

배경

#20 조사에서 block boundary Enter/Backspace는 headless command가 소유해야 한다고 정리했다. 하지만 Android/iOS virtual keyboard의 event ordering과 native effect는 jsdom replay나 desktop browser smoke만으로 닫을 수 없다.

ProseMirror-view와 Lexical changelog에는 같은 bug class가 반복된다.

• Android Backspace가 Enter로 해석됨
• Android virtual keyboard Backspace join이 Enter handler를 실행함
• Android code block Enter와 spell correction 충돌
• Chrome Android empty nested list item Enter native behavior 교체
• iOS empty heading Enter, native no-effect Enter, double paragraph Enter
• code block empty line Backspace와 Firefox cursor 위치 문제

근거

• docs/editor-block-boundary-key-policy-audit.md
• docs/editor-beforeinput-policy-audit.md
• ProseMirror-view changelog
  • https://raw.githubusercontent.com/ProseMirror/prosemirror-view/master/CHANGELOG.md
• Lexical changelog
  • https://raw.githubusercontent.com/facebook/lexical/main/CHANGELOG.md

수집할 trace

• Android Chrome / GBoard: paragraph start/end Backspace/Delete
• Android Chrome / GBoard: empty paragraph Backspace
• Android Chrome / GBoard: codeBlock Enter and newline Backspace
• Android Chrome / GBoard: empty listItem or whitespace-only listItem Enter
• iOS Safari: empty heading Enter
• iOS Safari: paragraph start/end Enter and Backspace
• iOS Safari: codeBlock Enter and newline Backspace

완료 기준

• 각 trace에 raw input event 순서, beforeinput.inputType, data, isComposing, selection before/after를 남긴다.
• native DOM effect가 있었는지와 command result가 충돌했는지 분리한다.
• 재현 가능한 trace는 fixture 또는 문서 evidence로 저장한다.
• current command policy를 바꿔야 하는 항목은 별도 구현 이슈로 분리한다.

[developer-1px]

현재 agent 환경에서는 이 이슈의 완료 기준을 충족할 수 없습니다.

완료 기준이 Android/iOS 가상 키보드의 실제 Enter/Backspace block-boundary event ordering, native DOM effect, command result 충돌 여부를 요구합니다. 로컬 jsdom, desktop Playwright, synthetic InputEvent는 Android Gboard/iOS Safari의 virtual keyboard behavior를 재현하거나 증명하지 못합니다.

필요한 다음 입력:

• Android Chrome+Gboard: paragraph start/end Backspace/Delete, empty paragraph Backspace, codeBlock Enter/newline Backspace, empty/whitespace listItem Enter
• iOS Safari: empty heading Enter, paragraph start/end Enter/Backspace, codeBlock Enter/newline Backspace
• 각 trace의 raw event order, beforeinput.inputType, data, isComposing, selection before/after, native DOM effect, command result

이 trace가 들어오면 current command policy 변경 필요 여부를 별도 구현 이슈로 분리할 수 있습니다.

[developer-1px]

Update after PR #126:

Added this issue to the repo-tracked manual trace collection contract.

• Manifest: tests/fixtures/manual-editor-traces/manifest.json
• Sample convention: tests/fixtures/manual-editor-traces/README.md
• Contract doc: docs/editor-manual-trace-collection.md
• CI guard: packages/editable/manualTraceCorpus.test.ts

Required scenarios now tracked in the manifest:

• ios-enter-backspace-boundary
• android-enter-backspace-boundary

Current status: still collecting. This issue should stay open until raw iOS/Android traces separate native DOM effect from model command result and capture event order, inputType/data/isComposing, target ranges, selection, history grouping, and undo behavior.

[developer-1px]

Current environment check:

• No Android device path is available here: adb is not installed/available.
• No iOS device/simulator target was listed through xcrun in this environment.
• Headless/browser emulation would not satisfy this issue's real Android/iOS Enter/Backspace block-boundary trace requirement.

Conclusion: #72 still requires real iOS/Android keyboard traces or a user-provided trace sample matching tests/fixtures/manual-editor-traces/manifest.json.

[developer-1px]

Update after PR #129:

Added a standalone manual trace recorder for this issue:

• Tool: tools/evidence/manual-trace-recorder.html
• Usage doc: tools/evidence/README.md
• Evidence doc: docs/editor-evidence-capture-tools.md

Target fixture paths:

• tests/fixtures/manual-editor-traces/issue-72/ios-enter-backspace-boundary.json
• tests/fixtures/manual-editor-traces/issue-72/android-enter-backspace-boundary.json

After capture, add the sample entry to tests/fixtures/manual-editor-traces/manifest.json. Refs PR #129.

[developer-1px]

Update after PR #130:

Added an evidence coverage CLI:

• pnpm run evidence:status prints current evidence coverage.
• pnpm run evidence:check fails until all required clipboard/trace evidence is present.

Current #72 status from the CLI: missing ios-enter-backspace-boundary and android-enter-backspace-boundary trace samples.

Refs PR #130.