Protect what matters – even after you're gone. Make a plan for your digital legacy today.
browser extension
21 Topics1Password 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.Solved9KViews18likes50CommentsSevere slowdown in Chrome with 1Password extension 8.11.12.27 on pages with many inputs
Since updating to 1Password extension 8.11.12.27 in Chrome, pages with forms containing thousands of inputs freeze on load. The problem also occurs with many hidden inputs, which should not be processed by the extension. We run an application that makes heavy use of hidden inputs. With earlier versions of the extension this was not a problem. Profiling shows high CPU use in openOrClosedShadowRoot(), especially when called on the form element containing many inputs. After load, the function runs instantly, so the slowdown is tied to the extension’s initial DOM scan. Steps to Reproduce: Install 1Password extension v8.11.12.27 in Chrome. Open a form with thousands of inputs, including hidden ones. Example: https://inputs-1password.netlify.app/ On load, clicking buttons or opening the context menu is impossible. Chrome stays frozen until the extension finishes scanning. Expected Result: Pages should load normally, regardless of number or type of inputs. Actual Result: Pages freeze during load due to heavy time spent in openOrClosedShadowRoot(). Impact: Severe slowdown in apps with large forms. Users blocked from working with affected pages. Disabling Autofill options does not help. Using "Hide on this page" does not help. Adding data-1p-ignore to every input is not feasible for us. Rolling back the extension is not practical. Workarounds: None viable for production. Proposed fixes: Optimize DOM traversal or revert to the previous methods. Support a parent-level attribute to exclude all children from scanning. Ensure that when the extension is disabled for a page, it truly does not inject or process elements on that page.Solved359Views2likes10Comments1password 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.50Views1like3Comments1PW 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 in312Views1like8Comments