Repository navigation
Recover first-frame Binance ladder input rollback - #198
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.
Root cause
Binance can restore a controlled ladder quantity input in a microtask after the userscript write returns but before the first animation-frame observation. Version 2.7.136 preserved recovery only for synchronous rejection or rollback after at least one observed matching frame, leaving this first-frame window uncovered. A natural Open Long reproduction confirmed the same empty controlled value with no diagnostic probe active.
Changes
Validation
npm test(371/371)npm run build:binance-orderbook-tradenpm run check:binance-orderbook-tradegit diff --check