Bitwarden autofill bug/error

Mattches · June 17, 2026, 5:30pm

I suspect that this is likely related to this issue that has been resolved and should be uplifted to the next stable update:

github.com/brave/brave-browser

Brave 1.91.171 blocks a redirect to a web extension url (chrome-extension://)

opened 06:50PM - 10 Jun 26 UTC

closed 12:01PM - 15 Jun 26 UTC

here-nerd

feature/extensions priority/P2 QA/Yes release-notes/include OS/Desktop

### Description Server-side (302) redirects from a web page to a `chrome-extens…ion://` URL never complete in Brave 1.91.171. The navigation hangs indefinitely: DevTools Network shows the request as "(pending)" forever, the tab URL never changes, and `tabs.onUpdated` / `webNavigation` events for the target URL never fire. No error page or interstitial is shown. This breaks OAuth/OIDC (PKCE) sign-in flows in extensions where the identity provider's redirect URI is an extension page declared in `web_accessible_resources`. **Regression window:** works in 1.91.168 (Chromium 149.0.7827.54), broken in 1.91.171 (Chromium 149.0.7827.103). Not reproducible in Chrome 149.0.7827.103 or Edge 149.0.4022.52 with the identical extension. ### Steps to reproduce 1. Load the attached minimal extension (MV3). It contains `callback.html`, declared in `web_accessible_resources` with `"matches": ["<all_urls>"]` (no `use_dynamic_url`): ```json "web_accessible_resources": [{ "resources": ["callback.html"], "matches": [""] }] ``` 2. In a normal (non-private) window, navigate to a URL that responds with `302 Location: chrome-extension://<extension-id>/callback.html?code=test` 3. Observe the tab and DevTools Network panel. [brave-redirect-repro.zip](https://github.com/user-attachments/files/28807759/brave-redirect-repro.zip) ### Actual result - The redirect target never loads; the tab stays on the redirecting page / blank. - DevTools shows the `chrome-extension://…` request stuck at status "(pending)" indefinitely — it is never finalized as failed or canceled. - `chrome.tabs.onUpdated` never fires for the target URL. ### Expected result The navigation commits and `callback.html` loads (as in Brave 1.91.168, Chrome 149.0.7827.103, and Edge 149.0.4022.52), or — if intentionally blocked — the navigation is cleanly canceled with a visible/observable error rather than deferred forever. ### Reproduces how often Easily reproduced ### Brave version (brave://version info) Brave 1.91.171 (Chromium 149.0.7827.103), macOS 26.3 ### Channel information - [x] release (stable) - [ ] beta - [ ] nightly ### Reproducibility - [x] with Brave Shields disabled - [ ] with Brave Rewards disabled - [ ] in the latest version of Chrome ### Miscellaneous information - Shields disabled globally and per-site: no change. - `brave://flags/#brave-debounce` disabled (full relaunch): no change. - Safe Browsing set to no protection: no change. - Per release notes, the 1.91.168→1.91.171 delta is small (Cardano/Origin fix, Survey Panelist setting removal, P3A first-launch fix) plus the Chromium bump 149.0.7827.54 → 149.0.7827.103, so the regression is likely either a brave-core change in that window or an interaction between Brave's navigation patches and the Chromium patch bump.

Topic		Replies	Views
Bitwarden autofill dropdown overlay missing globally after recent Brave update Brave Browser windows	2	827	June 25, 2026
Bitwarden's Autofill has been permanently disabled no matter what you do Browser Feedback windows , bug , feedback	2	118	August 26, 2026
Bitwarden Extension not working Brave Browser macos	1	5209	March 7, 2021
Bitwarden Extension no longer works properly Desktop Support macos	1	937	June 23, 2026
Brave on Android breaks Bitwarden Mobile Support android	2	2442	March 1, 2025
Brave stops autofilling with Bitwarden Mobile Support android	8	793	December 7, 2025
Bitwarden autofill not working in Brave Mobile Support android	1	3080	December 13, 2018
Password auto-fill with Bitwarden does not work on some websites Mobile Support bug , android	1	168	December 13, 2025

Bitwarden autofill bug/error

Related topics