Repository navigation
Conversation
Duplicate detection and auto-close were registered after async startup and kept their state in memory, so they stopped when Chrome unloaded the worker. Listeners now register at startup, and auto-close uses alarms. Co-authored-by: Cursor <cursoragent@cursor.com>
…er help The fork stays seeded from developerish/tab-count. The README names that project as the source and credits Auto for help on the service worker fixes. Co-authored-by: Cursor <cursoragent@cursor.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
chrome.storage.sessionand runs auto-close withchrome.alarmsinstead of an in-memorysetInterval.confirm().Test plan
tabJanitoralarm still exists in the extension service worker.node __tests__/manifest.test.jsMade with Cursor