iOS/Android touch selection 실기기 trace 수집

[developer-1px]

문제

#21 조사에서 mobile touch selection의 핵심 완료 조건인 iOS Safari/Android Chrome 실기기 trace가 아직 없음을 확인했다.

Desktop Playwright mobile viewport 또는 jsdom pointer replay는 native long press selection handles, mobile native menu, virtual keyboard, visual viewport, Android Gboard composition/selectionchange ordering을 증명하지 못한다.

근거

• 문서: docs/editor-mobile-touch-selection-policy-audit.md
• ProseMirror Android write-up은 Android on-screen keyboard와 contenteditable이 composition, beforeinput, selectionchange, keyboard visibility를 desktop과 다르게 섞는다고 설명한다.
• Lexical changelog와 PR #7297/#7309/#4395는 touch/mobile selection을 desktop pointer와 별도 처리한 사례다.

수집할 trace matrix

• iOS Safari
  • tap text caret
  • long press word selection
  • selection handle drag
  • native menu copy/cut/paste
  • touch scroll over editor
  • atom/figure adjacent long press
• Android Chrome + Gboard
  • tap text caret with keyboard
  • long press word selection
  • selection handle drag
  • native menu copy/cut/paste
  • touch scroll over editor
  • atom/figure adjacent long press

기록해야 할 evidence

• pointer/touch/contextmenu/selectionchange/input/beforeinput/composition event ordering
• native DOM selection anchor/focus와 canonical selection snapshot
• visual viewport/keyboard visibility 변화
• custom overlay visibility
• active text leaf flush 여부
• native menu action 전후 clipboard/cut/paste/delete 결과

완료 기준

• iOS Safari trace가 debug report 또는 fixture 형태로 저장된다.
• Android Chrome + Gboard trace가 debug report 또는 fixture 형태로 저장된다.
• trace에서 자동화로 재현 가능한 것은 Playwright/browser gate로 승격한다.
• 자동화 불가능한 native menu/handle gesture는 manual device gate로 문서화한다.
• touch selection·long press·mobile selection handle 실패 조사 #21 문서의 실기기 trace 미완료 항목을 갱신한다.

[developer-1px]

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

이 이슈는 iOS Safari와 Android Chrome+Gboard의 native touch selection handles, long press menu, virtual keyboard, visual viewport, native clipboard menu ordering을 실제 기기에서 기록해야 합니다. Desktop Playwright mobile viewport, jsdom pointer replay, synthetic touch events로는 native selection handle drag나 OS menu copy/cut/paste 결과를 증명할 수 없습니다.

필요한 다음 입력:

• iOS Safari debug trace: tap caret, long press word selection, handle drag, native menu copy/cut/paste, scroll, atom/figure adjacent long press
• Android Chrome+Gboard debug trace: same scenario set
• 각 trace의 pointer/touch/contextmenu/selectionchange/input/beforeinput/composition ordering, native DOM selection, canonical selection, visualViewport/keyboard visibility, clipboard result

이 데이터가 들어오면 자동화 가능한 부분을 Playwright/browser gate로 승격하고, native menu/handle gesture는 manual device gate로 문서화할 수 있습니다.

[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-touch-selection
• android-touch-selection

Current status: still collecting. This issue should stay open until real iOS Safari and Android Chrome traces capture selectionchange order, DOM selection before/after, mapped model selection, viewport state, native menu state, and which parts can be promoted to Playwright.

[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.
• Chrome extension browser backend is unavailable, so I cannot use an existing logged-in/mobile-debugging browser session from here.

Conclusion: #70 still requires a real iOS Safari and Android Chrome touch-selection capture on connected devices 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-70/ios-touch-selection.json
• tests/fixtures/manual-editor-traces/issue-70/android-touch-selection.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 #70 status from the CLI: missing ios-touch-selection and android-touch-selection trace samples.

Refs PR #130.

[developer-1px]

Update after PR #131:

pnpm run evidence:status now prints target fixture paths for every missing trace. Current #70 targets:

• tests/fixtures/manual-editor-traces/issue-70/ios-touch-selection.json
• tests/fixtures/manual-editor-traces/issue-70/android-touch-selection.json

Refs PR #131.