Protect what matters – even after you're gone. Make a plan for your digital legacy today.
1Password Chrome extension is incorrectly manipulating <code> blocks
The latest 1Password Chrome extension is incorrectly manipulating the DOM within <code> blocks on static pages. It looks it's using prism.js to try to add syntax highlighting to <code> blocks on the entire page. If you're using a static site generator to highlight code with a different library, it causes the display to break. Example: mkdocs, a popular documentation tool If you view the documentation for customizing Mkdocs material (https://squidfunk.github.io/mkdocs-material/customization/) with the extension enabled, you'll see that the YAML example at the top is not highlighted (it should be). Under the hood, if you inspect its DOM, you can see that it's been rewritten with prismjs classes. If you disable the extension, it is highlighted: This is likely to impact a number of documentation sites in the tech community.
1password input focus lag with lots of inputs
I'm running into an issue where 1password seems to significantly slow down interaction with the webpage I'm working on. There's a ton of input fields of which most are hidden, I cannot lower the amount of inputs, in fact I have to increase the amount of inputs due to how the system works. Every time I click on an input, the focus is delayed by ~200ms or so. The next time I select the same input field it's instant. 1password seems to do something that slows down the focus event. I made a performance recording in firefox. I selected 3 inputs and after the 3rd on selected the same 3 in the same order with no slowdown. I've tried adding data-1p-ignore and autocomplete="off" but it didn't solve anything.
Safari & Firefox extensions still break <pre>/<code> blocks after page load
Hi 1Password team 👋, I’m opening this discussion specifically for Safari and Firefox. While the original issue appears to be resolved for Chrome, the same behavior is still reproducible in other browsers. For reference, this is the original Chrome-related discussion: 1Password Chrome extension is incorrectly manipulating <code> blocks | 1Password Community Environment Tested on macOS with the following versions: Firefox: 146.0.1 (aarch64) 1Password extension: 8.11.23.2 (Dec 16, 2025) Safari: Version 26.2 (21623.1.14.11.9) 1Password extension: 8.11.22.27 Current status The issue is still present in: Firefox (reliably reproducible) Safari (very noticeable once the extension initializes) Observed behavior <pre><code> blocks render correctly on initial page load (syntax highlighting and line numbers are visible) As soon as the 1Password extension finishes initializing, the DOM is modified Syntax highlighting and line numbers disappear This happens without any user interaction, simply by enabling the extension The behavior matches the previously reported Chrome issue, but remains unresolved in Safari and Firefox. Why this matters Many developer-focused sites rely on client-side syntax highlighting (e.g. Prism, Highlight.js, Shiki). Post-load modification of code blocks breaks documentation and significantly impacts readability. Request The Chrome fix is very much appreciated 👍 It would be great to see the same behavior addressed consistently for Safari and Firefox, so code blocks are handled uniformly across all 1Password browser extensions. Thanks a lot for the continued work — and happy to help with further testing if needed. Wishing you all a happy new year 🎉 Best regards
1PW extension bug: autofill theme detection fails when using oklch color scheme
Hey, I am trying to fix the autofill background on a web app that has dark mode. Right now the 1Password extension applies light autofill background which creates unreadable contrast (1st screenshot). It's because input gets `data-com-onepassword-filled="light"` attribute with light variant. Is it possible to tell the 1PW that the page is using dark mode or what's the solution to let the 1PW set `data-com-onepassword-filled` to `'dark'`? I have set the color-scheme CSS property to `dark`. Edit: I managed to debug this issue and found out there's a bug in the theme detection by 1PW extension itself that's done via `data-com-onepassword-filled="light|dark"`. The reproduction is simple: When using `oklch` color on input text, the autofill detection breaks and resolves the theme always as light. <!DOCTYPE html> <html lang="en" style="color-scheme: dark"> <body> <h1>Working - uses hex</h1> <div style="color: #edeef0"> <input type="email" autocomplete="email" /> </div> <h1>Not working - uses oklch</h1> <div style="color: oklch(94.9% 0.003 264.5)"> <input type="email" autocomplete="email" /> </div> </body> </html> Which will result in
Customizing the suggested title when saving new password
The first time you sign into a new website and save the credentials in 1Password, it suggests a name, based on the domain name of that website. As a website owner, is there anything I can do to customize the formatting? For example, adding spaces and capitalization to make it more user friendly? For example, the suggested name for this site is "1Password".
Chrome plugin popup doesn't close anymore
On Chrome for Mac I have installed the 1Password plugin. Since recently, the popup that opens up prompting to save credentials won't close anymore no matter what I do - clicking on the 'x', clicking outside, pressing on the 'Unlock 1Password' button, hitting the Esc key. Chrome version: 141.0.7390.123 (Official Build) (arm64)
Chrome extension broken in dark mode when using oklch
This took me a bit to debug, and unfortunately I don't have a minimal reproduction available, but here's the issue, on a website I'm working on we use shadcn, which in turns uses OKLCH to define colors, which is not supported by the chrome extension at the moment. I found the code in the extension for this, and it expecting a RGB color: Would it be possible to update the extension to support OKLCH as well? For example this is the style I'm usingconsole logs: unable to filter out 1password logs in local development
As a front end developer, I have a feature request: the ability to turn off logs from the 1password extension. This could be just a checkbox to enable/disable logs, maybe a developer mode for debugging implementation which enables logs, anything! Maybe logging them as `console.debug` instead of `console.log`? A checkbox for disabling logs on `localhost` only? I love 1password, don't get me wrong. But the logs have been the bane of my existence when working on any web app involving authentication, because there's no way to filter out the logs. Example output: background.js:80 📤 Sending <NmLockState> message to native core <2920926948> 11:00:39.169 background.js:80 📥 Received message <NmLockState> from native core <2920926948>. Duration: 4.3ms 11:00:54.167 background.js:80 📤 Sending <NmLockState> message to native core <1746240738> 11:00:54.171 background.js:80 📥 Received message <NmLockState> from native core <1746240738>. Duration: 4.6ms 11:01:09.172 background.js:80 📤 Sending <NmLockState> message to native core <4161527562> 11:01:09.183 background.js:80 📥 Received message <NmLockState> from native core <4161527562>. Duration: 11ms 11:01:21.119 background.js:80 📤 Sending <NmLockState> message to native core <951950119> 11:01:21.151 background.js:80 📥 Received message <NmLockState> from native core <951950119>. Duration: 31.7ms 11:01:24.171 background.js:80 📤 Sending <NmLockState> message to native core <2174341925> 11:01:24.176 background.js:80 📥 Received message <NmLockState> from native core <2174341925>. Duration: 5.8ms 11:01:39.173 background.js:80 📤 Sending <NmLockState> message to native core <1407972505> 11:01:39.186 background.js:80 📥 Received message <NmLockState> from native core <1407972505>. Duration: 12.6ms 11:01:54.171 background.js:80 �� Sending <NmLockState> message to native core <2421987558> 11:01:54.184 background.js:80 📥 Received message <NmLockState> from native core <2421987558>. Duration: 13.1ms 11:02:09.172 background.js:80 📤 Sending <NmLockState> message to native core <630129950> 11:02:09.188 background.js:80 📥 Received message <NmLockState> from native core <630129950>. Duration: 15.8ms 11:02:21.119 background.js:80 📤 Sending <NmLockState> message to native core <964956985> 11:02:21.123 background.js:80 📥 Received message <NmLockState> from native core <964956985>. Duration: 4.5ms 11:02:24.171 background.js:80 📤 Sending <NmLockState> message to native core <3234675529> 11:02:24.177 background.js:80 📥 Received message <NmLockState> from native core <3234675529>. Duration: 5.8ms 11:02:39.170 background.js:80 📤 Sending <NmLockState> message to native core <714895378> 11:02:39.176 background.js:80 📥 Received message <NmLockState> from native core <714895378>. Duration: 5.5ms 11:02:54.171 background.js:80 📤 Sending <NmLockState> message to native core <1997105720> 11:02:54.178 background.js:80 📥 Received message <NmLockState> from native core <1997105720>. Duration: 7.5ms 11:03:09.173 background.js:80 📤 Sending <NmLockState> message to native core <1243253266> 11:03:09.199 background.js:80 📥 Received message <NmLockState> from native core <1243253266>. Duration: 26.2ms 11:03:21.175 background.js:80 📤 Sending <NmLockState> message to native core <3734071001> 11:03:21.181 background.js:80 📥 Received message <NmLockState> from native core <3734071001>. Duration: 6.5ms 11:03:24.171 background.js:80 📤 Sending <NmLockState> message to native core <1854610928> 11:03:24.173 background.js:80 📥 Received message <NmLockState> from native core <1854610928>. Duration: 2.6ms 11:03:39.171 background.js:80 📤 Sending <NmLockState> message to native core <3181823558> 11:03:39.176 background.js:80 📥 Received message <NmLockState> from native core <3181823558>. Duration: 4.7ms 11:03:54.171 background.js:80 📤 Sending <NmLockState> message to native core <3797715197> 11:03:54.180 background.js:80 📥 Received message <NmLockState> from native core <3797715197>. Duration: 8.8ms 11:04:09.171 background.js:80 📤 Sending <NmLockState> message to native core <2885493011> 11:04:09.177 background.js:80 📥 Received message <NmLockState> from native core <2885493011>. Duration: 5.5ms 11:04:18.049 background.js:80 📤 Sending <NmLockState> message to native core <386599336> 11:04:18.052 background.js:80 📥 Received message <NmLockState> from native core <386599336>. Duration: 3.2ms 11:04:24.171 background.js:80 📤 Sending <NmLockState> message to native core <3057763534> 11:04:24.177 background.js:80 📥 Received message <NmLockState> from native core <3057763534>. Duration: 6.6ms 11:04:39.171 background.js:80 📤 Sending <NmLockState> message to native core <3449831082> 11:04:39.174 background.js:80 📥 Received message <NmLockState> from native core <3449831082>. Duration: 3.1ms I've also found these other relevant posts on the same issue with no solution: How to silence 1Password noise in the browser console | 1Password Community Chrome extension background.js logs and/or errors in console | 1Password Community Sending <NumLockState> messages | 1Password Community
