Repository navigation
fix: retain data panel sessions across tab switches - #321
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.
Switching between Binance tabs used to stop both data panels and initialize them again on return, clearing CMC rows and repeating clock, funding, and historical requests. Keep activated route sessions, in-flight requests, displayed values, and expanded details across visibility changes; only fetch again when the foreground deadline is due.
Release Trading Data 1.2.2 and CoinMarketCap Data 0.2.2 with rebuilt install artifacts and updated lifecycle documentation.
Validation: full
npm testpassed 2548/2548, including 23 background lifecycle scenarios; the generated-panel Playwright suites passed 41/41. Both builds, syntax and metadata checks, test lint, andgit diff --checkpassed. Independent read-only review approved the final implementation. Rendered browser output was inspected. Visibility and suspended animation frames were simulated; live Chrome throttling/freezing, Tampermonkey installation, and live Binance responses were not exercised.