Skip to content

test(browser): await settled editor selection and owned responses - #28

Merged
mysbryce merged 3 commits into
mainfrom
fix/rich-text-list-caret-0.28.1
Oct 11, 2026
Merged

mysbryce merged 3 commits into
mainfrom
fix/rich-text-list-caret-0.28.1

Conversation

@mysbryce

@mysbryce mysbryce commented Oct 11, 2026 •

Copy link
Copy Markdown
Owner

Browser fixtures now wait for custom menus to close and restore trigger focus before native editor keys or phone Save focus. List and quote stories require an exact, focused, collapsed text-end caret that remains stable across two animation frames before their unchanged native line-break keys. API-sharing fixtures release and await their owned delayed responses and drain proxy handlers before stopping the backend.

The latest correction covers Quote → ArrowRight → Shift+Enter. Native typing, five-second assertion budgets, Undo/Redo, exact DOM text and saved AST assertions remain intact. Production sources, dependencies, the Lexical history patch and CI configuration are unchanged. Source supports deferred menu focus ordering; the exact hosted failure mechanism remains unproved. This does not establish a production data-loss fix.

Current 0.28.3-alpha.0 checks:

  • Unchanged built quote baseline and strengthened journey each pass three repetitions, in 22.15 and 22.11 seconds browser total. The initial missing-build invocation is not valid quote verification.
  • Core passes types, build, whole formatting and 416 backend cases / 9,640 assertions in 42.73 seconds backend time.
  • Complete explicit-two-worker E2E passes all 81 cases in 353.39 seconds, including isolated member-profile and cold Vite/WebSocket phases. Browser defaults and CI remain unchanged.
  • Fresh focused Quote capture passes ten images. All ten light-desktop originals pass current-byte review; no full gallery is recaptured or promoted.
  • Fresh portable acceptance passes all 11 cases / 1,265 assertions in 123.37 seconds, including the actual copied-executable browser in 18.77619 seconds. An initial missing-artifact-path harness guard invocation ran no artifact journeys; only its required process environment was corrected.
  • Actual Bun 1.4.2 executable metadata identifies version 0.28.3 and the tested working-tree candidate based on 8f6c73d; 1,017 runtime inputs, 713 original notice files / 276 components and 77 observed npm components verify with zero new scopes.

All 14 fresh copied-executable originals pass individual current-byte review with opaque key masks and readable light/dark desktop and phone controls. Some canvas content remains behind settings and long phone URLs stay bounded in their inputs. Release policy and the clean source bundle pass at commit 36d65d9b1d081c0ad01bd66215b6d00921e71c10: 1,056 indexed files / 24,526,564 bytes with exact source and payload hashes. No GUI GraphQL, native-language certification, full-gallery promotion, tag or new public binary release is claimed.

Prior hosted evidence stays explicit: PR #27 head CI passed but main CI failed the list journey. Intermediate 0.28.1 head CI failed pre-Enter caret readiness, phone Save focus and sharing teardown transport. 0.28.2 head CI 38132151814 passes those three stories and core; its only browser failure is Quote losing its first literal text, after 78 passes. Its portable phase is skipped. New exact-head/main CI remains pending; retain both delivery branches until successful main acceptance and reviewed-tree proof.

@mysbryce mysbryce changed the title test(editor): wait for stable native list caret test(browser): await menu focus and owned responses Oct 11, 2026
@mysbryce mysbryce changed the title test(browser): await menu focus and owned responses test(browser): await settled editor selection and owned responses Oct 11, 2026
@mysbryce
mysbryce merged commit 5615ffd into main Oct 11, 2026
3 checks passed
@mysbryce
mysbryce deleted the fix/rich-text-list-caret-0.28.1 branch October 11, 2026 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant