Repository navigation
Fix Slice gesture timing in Linux UI CI - #97
Merged
Merged
Conversation
…bgl-context-recovery
…ontext-recovery verification
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.
Main UI CI sent synthetic Slice gestures before the deferred redraw finished, using clipped canvas bounds as the complete grid. This could miss the first touch edit or select the wrong cell. The helpers now wait for rendered grid dimensions and queued frames, then target cells on the full virtual scroll surface. Exact source, CRLF/download, Undo/history and navigation assertions are unchanged; the viewer runtime and site pin stay unchanged.
Validation:
Failure: main UI run 38090326009. Detailed reproduction and suite receipts are in docs/evidence/viewer-context/README.md. Actual unsigned agent:codex provenance was recorded and pushed for all three feature commits after the gate passed. Standalone Attest verification rejects the unchanged signature requirement and reviewer allow-list; configured progressive Trust passed with that degradation. No trusted signature, human diff review or lifecycle acceptance/archive is claimed.