Chromium engine: chrome.tabs.query({active, currentWindow}) from an action popup returns no tab, so tabCapture extensions (川流字幕 Subruu) can't start
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, macos, swift
- Domain
- api
Research direction
Start by tracing Chromium extension tab handling around chrome.tabs.query({active:true, currentWindow:true}), then compare with the embedder-owned tab patches 0026, 0119 and 0136 mentioned in the issue. The report does not identify the relevant source files or a Chromium end-to-end test, so first locate the query implementation and existing extension tests. Done means the popup receives the active YouTube tab and the extension can proceed to its capture startup flow.
Written by the indexing model from the issue text.
Description
Environment
- Yab 0.48.0 (build 202611161400), macOS, Chromium engine, Personal space (shared sign-in)
- Extension: 川流字幕 Subruu,
fdhjjimjclphneajgcajolflaodiblkp, v0.1.777.41 (Chrome Web Store). MV3; permissions includetabs,activeTab,tabCapture,offscreen,scripting(all granted, no disable reasons).
Steps
- Install the extension from the Chrome Web Store and sign in. Sign-in works.
- Open a
youtube.com/watchvideo and click the extension's toolbar button. The popup opens. - Press start.
Reproduces both in a pinned tab shared across spaces and in a normal new tab (⌘T, paste URL, play video).
Expected
Captions start, as in Chrome.
Actual
The start fails within ~150 ms with 請重新開啟插件並確認目前影片。 ("please reopen the extension and confirm the current video"), recorded by the extension's own startup diagnostics at popup.js:1:35733. That error is only thrown when the popup has no target tab URL. The popup gets its target from chrome.tabs.query({active:true, currentWindow:true}), so in Yab that call returned no tab, or a tab without a url. The request never reaches the service worker and tabCapture.getMediaStreamId is never called.
In 0.47.10 the same flow instead stalled in the service worker after the popup handed off and before capture began (diagnostics stuck at step begin, never reaching start-enter). Between those steps the worker only calls chrome.tabs.get(tabId), chrome.permissions.contains({origins:["https://www.youtube.com/*"]}), chrome.storage.local.set and chrome.tabs.sendMessage (700 ms timeout). Both versions point at extension tab lookups for the popup's page.
Notes
- Possibly related: patches 0026, 0119 and 0136 (embedder-owned windows and tabs, concealed producers, embedded tab operations). I couldn't find a Chromium-side end-to-end test for
tabCapture/offscreen, only WebKit ones. - I couldn't collect console output: the popup has no right-click Inspect,
chrome://extensionsandchrome-extension://pages can't be opened, and there's no way to enable remote debugging on the installed app (YAB_HELPER_ARGSis only read whenStore.testing). A supported way to inspect an extension's popup / service worker would help debug issues like this.
- Dominant language
- Swift
- Stars
- 648
- Forks
- 56
- Avg merge
- 21h 14m
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yetanotherbrowser/yab
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yetanotherbrowser/yab#1008 ·
Maintainers usually reply within 2 days
-
area: passwords Broken bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yetanotherbrowser/yab#923 ·
Maintainers usually reply within 2 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yetanotherbrowser/yab#918 · 1 reaction ·
Maintainers usually reply within 2 days
-
iPhone: the + button and the checkmark sit on top of the Space switcher in the bottom barPossibly taken @ChaseRoofener claimed this 3 days ago. OpenAnnoying area: iphone bug needs info
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yetanotherbrowser/yab#915 · 3 comments ·
Maintainers usually reply within 2 days
-
CONTRIBUTING.md and CI run scripts/runs/tests_for.py, which is not in the repositoryPossibly taken @serafimcloud claimed this 3 days ago. OpenAnnoying in progress
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
yetanotherbrowser/yab#875 · 1 comment ·
Maintainers usually reply within 2 days
All issues in yetanotherbrowser/yab
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
swiftlang/swift-org-website#1608 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
haacked/switchboard#460 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
manaflow-ai/cmux#47572 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
borrowcheckmate/swimlie#48 ·
Maintainers usually reply within 1 day