Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Forum Discussion
1P_Blake
Community Manager
Community ManagerPSA: Extension going blank or unresponsive in Chrome? Here's what we know
Hey everyone! We've been tracking a recent Chrome change that’s causing the 1Password extension to go blank or become unresponsive after filling on certain sites, and wanted to share what’s going on.
A change in Chrome 147 has introduced an issue with how the browser handles extensions and its back/forward cache. We have seen reports of this issue affecting other password managers too, so it’s not only 1Password.
We are in direct contact with the Chrome team and they're working on a fix. We anticipate a Chrome update on Wednesday will resolve this problem, and we’ll keep you informed if that timeline changes. Brave and Edge users on version 147 will also be affected since they share the same Chromium engine.
In the meantime, if the 1Password extension displays a blank screen or otherwise becomes unresponsive, fully quitting and reopening your browser should get things working again. Not ideal, we know, but it does the trick until the fix is rolled out.
We'll update this post when the fix ships. If you're seeing this and want to follow along on the Chromium side, here's the bug report.
3 Replies
1P_Blake Given the disruption of a foundational behavior of the software, why is it that 1Password isn't using its status service to make users aware of incidents like this? It does for many less frequently used features (as I write this, there is one impacting SSO for example and that is also due to a third-party cause for example). It's great to clearly post it in the community but that's a venue not many look at and not what we're told to follow to understand if there are availability disruptions. Surely something so central to the use of the software deserves using the status mechanism provided rather than making users actively search to determine if it's their own issue or 1Password's.
Also... Are Chromium builds not available for 1Password to regression test against before they are released to the public channel? If so, is 1Password doing what it can to discover potential integration/regression issues before they impact paying customers? I'd venture Chromium represents a massive segment of usage. We're not talking about edge cases here.
Couldn't agree more here. How can a software developer as prominent as 1Pass not be doing regression testing against pre-release builds of Chrome, or being more upfront with it's customers? I understand one or the other, but both? I only discovered this post after frustration-posting about the issue on X...
Thanks for the update. I was going crazy with this. Really frustrating. I'm on Linux running Chromium and I see the same issue.
