OS autocorrect·insertReplacementText history 실브라우저 trace 수집

[developer-1px]

배경

#14 조사에서 insertReplacementText는 phase 밖에서는 plain selection replacement command 하나로 처리한다는 정책을 세웠다. 하지만 macOS/iOS/Android autocorrect와 writing suggestion의 실제 event order는 current jsdom tests로 닫지 않았다.

근거

• docs/editor-composition-history-policy-audit.md
• docs/editor-beforeinput-policy-audit.md
• W3C Input Events Level 2는 insertReplacementText를 spell checker, auto-correct, writing suggestions 계열 inputType으로 정의한다.

수집할 것

• macOS Safari/Chrome, iOS Safari, Android Chrome 중 가능한 환경에서 autocorrect/replacement trace.
• beforeinput.inputType, data, isComposing, input, selectionchange, 최종 DOM/canonical text.
• Replacement가 composition phase 안/밖에서 어떻게 보이는지.

완료 기준

• 최소 1개 실제 browser/OS autocorrect trace가 남아 있다.
• editor policy가 command replacement, composition owner, reset 중 어디로 가야 하는지 분류되어 있다.

[developer-1px]

Blocked in this headless Playwright environment: the completion criterion asks for at least one real OS autocorrect / writing-suggestion trace from macOS/iOS/Android. Synthetic \ can validate editor policy, but it would not satisfy the requested OS autocorrect trace. This issue should be resumed with a real device/OS input source trace.

[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:

• macos-text-replacement-acceptance
• ios-autocorrect-prediction

Current status: still collecting. This issue should stay open until raw real-browser/OS traces capture event order, inputType/data, target ranges or payload shape, selection before/after, history grouping, and undo behavior.

[developer-1px]

Current environment check:

• macOS has enabled system text replacement entries in NSUserDictionaryReplacementItems.
• Headless Playwright/Chromium typing into a spellcheck/autocorrect-enabled contenteditable produced only insertText events for a test string and did not produce insertReplacementText.

Conclusion: Playwright keyboard.type() is not a valid source for #85 because it bypasses the OS replacement/autocorrect input path. A valid trace still needs an interactive real browser/OS input path, e.g. Safari/Chrome with real keyboard input or iOS/Android prediction/autocorrect UI.

[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-85/macos-text-replacement-acceptance.json
• tests/fixtures/manual-editor-traces/issue-85/ios-autocorrect-prediction.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 #85 status from the CLI: missing macos-text-replacement-acceptance and ios-autocorrect-prediction trace samples.

Refs PR #130.