Not sure if this is the way to report issues, but for the past couple of weeks, the autofill feature, and the right-click->autofill->login option no longer populates the password field on the https://client.schwab.com/ site. You can still copy the password and paste it into the field, so this isn’t a crisis. But obviously something has changed.
I am running Chrome on a Windows 11 PC. I have cleared my browser cache. I have synched my vault. This occurs on multiple computers.
Hello and welcome to the community! 
I’m just adding a note that I tested this with the Bitwarden extension 2025.12.0 on both Firefox and Edge, and they both autofilled normally from the right-click as stated above.
I note that the login form is in an iframe with a different host than the top page, i.e.,
<iframe id="lmsIframe" allow="publickey-credentials-get https://sws-gateway-nr.schwab.com" src="https://sws-gateway-nr.schwab.com/ui/host/?clientid=schwab-secondary&redirecturi=https%3a%2f%2fclient.schwab.com%2fAreas%2fAccess%2fSignOn%2fAuth" scrolling="no" aria-label="Login widget"></iframe>
which worked normally when the matching is set to the base domain for both browsers.
I don’t use Chrome, but I would have tried:
- Putting
https://sws-gateway-nr.schwab.comas a URL in the entry. - Using the above src URL, i.e.,
https://sws-gateway-nr.schwab.com/ui/host/?clientid=schwab-secondary&redirecturi=https%3A%2F%2Fclient.schwab.com%2FAreas%2FAccess%2FSignOn%2FAuth, as a Login URL directly.
P.S.: I changed the tags to reflect your post.
just for feedback. I tried Chrome on Windows 11 and it autofills fine with this URL
PS I initially used ctrl+shift+L then the right click menu. both worked
@MPantz Welcome to the forum!
Just in general: Of course, you can always post such things here in the forum and get assistance, if possible.
If you really want to report sites with autofill issues, however, you should use these official Google forms:
- Report autofill issues (other clients): Report auto-fill failure
- Report autofill issues (mobile apps): Report mobile autofill failure
Thanks for the quick feedback. I have many other passwords and websites and they all autofill without a problem. I love BitWarden, so this certainly isn’t a crisis. It’s just strange that only the Schwab site no longer works. And the problems only surfaced in the past couple of weeks.
I just tested further. If I go to the “client-home” version of the schwab.com page, the Login ID and Password fields (which are across the top of the page) autofill properly. On the “Areas/Access/Login” version of the page (with the login fields inside a box lower down on the page), the Login ID used to fill in, but not the password. Now, after mucking around for a while, neither field is populated. So I’m making it worse. But I can always copy and paste.
I’m obviously missing something. But thanks again. I have a workaround (the client-home option) and I’ll keep trying.
I can autofill on that page – here done with keyboard shortcut and with the inline autofill menu:
I think as @Neuron5569 already wrote, when you add https://sws-gateway-nr.schwab.com as an URI, then the autofill warning, you would get, can be removed.
Apart from that, using https://www.schwab.com with “base domain” – or https://www.schwab.com and https://client.schwab.com if you are using “host” matching – should be sufficient.
OK then. “Areas/Access/Login” still not working for me, but obviously the problem is unique to me.
I tried the long “sws-gateway-nr” URL provided by Neuron5569 and I do get autofill for that log-in page. So now I have 2 page options that work (including “client-home”) and 1 that still doesn’t. I can live with that.
For the record, when I click on the “Login ID” field on the “Areas/Access/Login” page, I DO get the list of passwords and I can select one. But only the Login ID field gets populated. Since BitWarden is finding the website and offering the IDs and passwords, I don’t think the problem is in the matching. It just doesn’t fill in the password field, for whatever reason.
I definitely appreciate everybody’s effort here. I have a work-around (actually 2). This is probably not worth any more of your time. Thanks!
I did also report this on the Google form, as suggested by Nail1684. So I guess now I’ll also cause others to scramble for this minor issue. Sorry about that.
I also cannot reproduce your issue (i.e., it autofills both the username and password for me without problems).
Yet another work-around to try would be to define a custom linked field (linked to your Password), with the custom field label set to passwordinput. Perhaps this shakes something loose for you.
Other than that, I would suggest disabling all browser extensions other than Bitwarden (e.g., allow Bitwarden to run in Incognito mode, but do not allow other extensions to run in Incognito), and checking whether you can now autofill the Schwab site.
@MPantz You’re not the only one experiencing this issue. It’s been going on for at least a month for me. I’ve seeing exactly the behavior you described (running Chrome 143.0.7499.193 and Bitwarden extension 2025.12.1) when using this page - https://client.schwab.com/Areas/Access/Login . Login ID field is populated by Bitwarden, Password field is not.
Using the long URL that Neuron5569 provided above works. I’m also able to autofill the login fields on https://www.schwab.com/client-home .
This works around the problem for me though there seems there’s something strange going on with https://client.schwab.com/Areas/Access/Login
@msaxer Welcome to the forum!
I can autofill both the Login ID and Password without issues on https://client.schwab.com/Areas/Access/Login using Chrome 144.0.7559.97 (in Incognito mode, in case that is relevant), with Bitwarden browser extension version 2025.12.1.
Have you tried my suggestions from the comment above? Does updating your Chrome browser help?
Thanks Martin. I appreciate the confirmation that I’m not crazy. My Chrome browser and Bitwarden extension are both updated to the latest. The https://client.schwab.com/Areas/Access/Login link still doesn’t work for me. Something about the box (frame?) around the username/password entry fields is confusing the extension’s ability to determine where to put the text. If I click on the appropriate Log-In item from the “Autofill suggestion” list in the browser extension pop-up, I get an error message that says “Unable to autofill the selected item on this page. Copy and paste the information instead”.
As indicated, I’ve switched over all my bookmarks to use the “client-home” link, and I’m good to go. Thanks again to all for commenting.
Thanks for the welcome @grb
Curious that page works for you since it definitely doesn’t for me. I’m running Chrome 144.0.7559.97 and Bitwarden extension 2025.12.1 in Incognito mode with no other extensions enabled in Incognito mode (I was hoping that the cause of my issue was another extension).
Inspecting the extension’s service worker in dev tools provides a fairly useless error message:
background.js:2 Uncaught (in promise) Error: Did not autofill.
at YT. (background.js:2:2835603)
at Generator.next ()
at s (background.js:2:2829158)
One other thing I checked was if NextDNS might have been blocking something. Doesn’t appear to be the case.
I see the same behavior in Edge and Brave (no surprise due to the shared Chromium base). What is surprising is I also see this behavior in Firefox.
Since I have a couple workarounds, I’m all good. Thanks for looking into this little mystery.
I posted 16 days ago that Auto-fil was working on the Schwab login. Today it isn’t.
I can still Copy and paste but Auto-fill shows as below, I tried Brave, Firefox and Chrome.
Unless there has been an extension update in the last 16 days (I’m on 2025.12.1 at present, 16 days ago would likely have 2025.12.0) then it is confusing?
FWIW, I can still autofill like it was 16 days ago.
Similar as others, was filling the username but not password. Works at Charles Schwab | A modern approach to investing & retirement | Charles Schwab .
Did anyone ever figure this out? My autofill for client.schwab.com works fine on one PC, but on another I’m having this exact issue. I can’t figure out what the difference might be.
@mgittelman Welcome to the forum! On the PC where autofill is not working, do you see your Schwab account in the browser extension’s “Autofill Suggestions”? Are you using the same browser on both PCs? Is the version of the browser and of the Bitwarden browser extension the same on both PCs?
Yes, schwab account is listed in the browser’s extension. I am using the same browser on both PC’s. On the one having issues, I have tried chrome, edge, and firefox. Exact same issue. The version of the extension is the exact same type.
I was working with claude for a while on this, and here is it’s summary of what we did. I must admit, it’s a bit more technical than I am, but I think it’s summary is pretty accurate and comprehensive. These are the times we live in now I suppose:
Summary
Bitwarden successfully autofills the username field but fails to fill the password field . This occurs on one specific Windows 11 machine across every browser tested. The same Bitwarden account, vault entry, and settings work correctly on another Windows 11 machine, an iPad, and via the alternative URL schwab. com/client-home
Environment
Affected machine:
-
OS: Windows 11 25H2 (Build 26200.8037)
-
Browsers tested: Brave 1.88.138, Chrome, Edge, Firefox (fresh install) — all fail identically
-
Bitwarden extension: 2026.2.0
-
Bitwarden desktop app installed and connected
-
No security software, no GPO, no MDM, no browser policies
Working machine:
-
OS: Windows 11 25H2 (Build 26200.8037)
-
Browser: Brave 1.88.136 — autofills successfully
-
Bitwarden extension: 2026.2.0
-
Same vault entry, same settings, same extensions installed
Technical findings
The login form at client.schwab.com/Areas/Access/Login embeds a cross-origin iframe served from sws-gateway-nr.schwab.com. Bitwarden detects the page and fills the username field successfully, but the password field remains empty.
Browser console errors on the affected machine:
-
postMessage event sent from unrecognized origin, ignoring message -
TypeError: can't access property 'includes', autoFillFieldData.autoCompleteType is null
Note: error #2 appears to be the cosmetic null-check bug already being tracked and addressed by the Bitwarden team (PR #19604). It is not the root cause of the autofill failure. The relevant error is #19604.
Key finding: When navigating directly to the iframe URL — sws-gateway-nr.schwab.com/ui/host/?clientid=schwab-secondary&redirecturi=https%3A%2F%2Fclient.schwab.com%2FAreas%2FAccess%2FSignOn%2FAuth — autofill works correctly on the affected machine. The failure only occurs when that page is embedded as a cross-origin iframe inside client.schwab.com.
Network analysis: Schwab serves identical JavaScript to both machines (filenames and hashes match), ruling out server-side A/B testing or geolocation-based code differences as the cause.
What has been ruled out
-
Browser or profile-specific issue — fails across all browsers including a fresh Firefox install with no extensions
-
Extension conflicts — identical extensions on both machines; fresh Firefox has none
-
Bitwarden settings — verified identical on both machines
-
Bitwarden extension local storage — empty on both machines (no legacy state carried over from older versions)
-
Browser flags — all default on both machines
-
Browser policies — no policies set on either machine
-
Network/IP — full tunnel VPN to home network made no difference
-
Cookie/storage state — clearing all cookies and storage made no difference
-
Security software — none installed on affected machine
-
GPO or MDM — personal machine, confirmed none
Workaround
Autofill works correctly on schwab .com/client-home , which renders the login fields outside of a cross-origin iframe.
Hypothesis
The postMessage event sent from unrecognized origin error suggests that Bitwarden’s content script communication across the cross-origin iframe boundary is failing on this machine. Since it fails across every browser engine (both Chromium-based browsers and Firefox), it appears to be something at the OS or environment level affecting cross-origin postMessage handling — but every obvious candidate has been ruled out.
Bitwarden reached out to me saying that https://github.com/bitwarden/clients/pull/19604 contains the fix. I am not so sure that that is it though. This problem has been around since I first installed the extension on this PC about 8 months ago. Various versions of the extension and browsers have been installed since then.
What happens if you add the URL sws-gateway-nr.schwab.com in a second “Website (URI)” field in the Schwab login item?