fix(plume): invalidate one frame on the active stop transition - #76
Merged
petekp merged 17 commits intoSep 9, 2026
Merged
Conversation
…nd the browser hit-tests the real page Claude-Session: https://claude.ai/code/session_01Ybe6Jiec8UUdHbyuQi9pjL
Adopt retained HTML API with sharp rendering defaults
Refine landing-page shadows, lamp glass, and flexible postcard
Fix Surface regressions and remove obsolete code and guidance
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
1 participant
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.
Plume now requests a final frame when animation stops, so Restore can draw the updated particle buffer without relying on an already queued render. The frame loop continues scheduling only while animation is active.
Closes #51.
The added test pins the mid-flight Restore transition back to held text. Ten Plume law tests, four typechecks, lint, and the full strict Chrome Plume gate pass. The browser gate covers native value/caret retention, same-buffer Restore, controls, mobile layout, and no-flag fallback. The original timing-dependent freeze was not independently reproduced as a before/after contrast; the change makes the final redraw explicit.