Repository navigation
Keep clipboard confirmations tied to the current scenario - #32
Merged
Merged
Conversation
dev-belly
marked this pull request as ready for review
November 2, 2026 04:34
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.
A slow clipboard write can finish after the visitor edits a timestamp and display 'Scenario link copied' beneath a different scenario. Capture the link at click time, serialize pending writes across edits, and announce success or fallback only while that exact link is still the visible valid scenario. Restore the button according to current validity when the write finishes.
Add real-Chrome controls for delayed success after a scenario switch, duplicate clicks, delayed rejection after invalid input, current failure/fallback and successful retry at desktop and 390px widths. Clipboard promises are controlled so the checks do not write to a runner's actual clipboard. Existing selection, download and independent Python replay checks remain in place.
Validation: real Chrome passes 38 interaction checks across seven visits at observed 1280px/390px widths, including both actual downloads and their independent replay. The shipped core passes 71 scenarios against SQLite and the independent Python engine; all 68 valid exported inputs independently replay. The local suite reports 152 tests with 16 optional pandas skips, zero failures/errors. UI/test script syntax, Ruff and git diff --check pass. Package runtime, data contracts, release assets and timing algorithms are unchanged.