Repository navigation
test(browser): await settled editor selection and owned responses - #28
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.0checks: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
38132151814passes 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.