v1.0.9 — stop blocking Subscriptions/You tabs and restore frame rate#13
Merged
Conversation
- Narrow PLAYER_CONTAINER_FRAGMENTS to ["player"] only. The previous
list ("pager"/"recycler"/"container") matched the Shorts shelf
embedded in the Subscriptions and "You" feeds, so v1.0.8 back-pressed
those tabs as soon as they loaded.
- Register only typeWindowStateChanged. typeWindowContentChanged fires
at ~30 Hz during YouTube scroll; even with the v1.0.8 throttle the
dispatch cost itself dropped frame rate. State-changed fires only on
real screen transitions, which is when detection needs to re-run.
- Bump versionCode 9 -> 10, versionName 1.0.8 -> 1.0.9.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
Two regression fixes from v1.0.8.
PLAYER_CONTAINER_FRAGMENTSmatchedpager/recycler/container, which appear on the Shorts shelf embedded in those feeds. Narrowed to["player"]only — the full-screen Shorts player still hasPlayerin its class name, so detection there is unchanged.typeWindowContentChangedfires at ~30 Hz inside YouTube; even with the v1.0.8 250ms throttle, the dispatch cost alone tanked frame rate. Now registering onlytypeWindowStateChanged, which fires on real screen transitions (opening Shorts, switching tabs, navigating to a video) — exactly when detection needs to re-run.Test plan
🤖 Generated with Claude Code