Skip to content

fix(extension): explain missing browser debugger API - #776

Open
Kidz0419 wants to merge 1 commit into
Tencent:mainfrom
Kidz0419:codex/browser-debugger-compatibility
Open

Kidz0419 wants to merge 1 commit into
Tencent:mainfrom
Kidz0419:codex/browser-debugger-compatibility

Conversation

@Kidz0419

Copy link
Copy Markdown

When a Chromium browser omits part or all of chrome.debugger, the background worker can fail before starting the connection, leaving the popup with generic daemon and port troubleshooting.

Check the required debugger methods and events before initializing the worker. The popup performs the same check independently and directs people to desktop Chrome or Edge when the API is unavailable. This also updates the compatibility docs, both changelogs, and all shipped popup locales.

Fixes #773.

Testing

  • pnpm ext:test — 4,105 passed, 8 skipped.
  • pnpm --filter @browser-skill/i18n test — 64 passed.
  • Extension TypeScript compile, pnpm lint, pnpm ext:build, and the changelog sync check passed.
  • In Chromium 156 with disposable profiles, the stock build showed the normal connection controls and attempted a WebSocket upgrade. A copy with the debugger permission removed showed the compatibility alert and made no connection attempt during a 1.5-second observation window. The reported Android browser was not tested directly.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

扩展在缺少 chrome.debugger 的浏览器上静默失败,错误提示误导(Xiaomi Browser / Android 13)

1 participant