Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
1Password classing input element as a username field
I am developing a React web application. On one page, I have an input element which takes a value which has nothing to do with 1Password credential or form filling, yet 1Password adds its icon to the right hand side. When I click the icon, it's not even like it's trying to autofill my details as if it were a registration form, it clearly thinks it's a username field. I realise I can add the parameter 'data-1p-ignore' to the element, but could someone explain why 1Password thinks this is a field it can autofill a username into? Is it simply because the id/name attribute has the string 'name'? I also would've assumed that autocomplete="off" would also have prevented 1Password from interacting with this element, but perhaps I'm wrong. I'd rather not have to add the 'data-1p-ignore' element to every field as this makes the code messy and just feels like a hack rather than a solution. The element in question is below, which for what it's worth, is inside a <form> tag along with another field and a submit button. Since it's a React application, this is the generated markup: <div role="group" data-slot="field" data-orientation="vertical" class="group/field flex w-full gap-3 data-[invalid=true]:text-destructive flex-col *:w-full [&>.sr-only]:w-auto" > <label data-slot="label" class="flex items-center gap-2 text-sm leading-none font-medium select-none group-data-[disabled=true]:pointer-events-none group-data-[disabled=true]:opacity-50 peer-disabled:cursor-not-allowed peer-disabled:opacity-50" for="mc_name" >Name</label ><input data-slot="input" class="h-9 w-full min-w-0 rounded-4xl border border-input bg-input/30 px-3 py-1 text-base transition-colors outline-none file:inline-flex file:h-7 file:border-0 file:bg-transparent file:text-sm file:font-medium file:text-foreground placeholder:text-muted-foreground focus-visible:border-ring focus-visible:ring-[3px] focus-visible:ring-ring/50 disabled:pointer-events-none disabled:cursor-not-allowed disabled:opacity-50 aria-invalid:border-destructive aria-invalid:ring-[3px] aria-invalid:ring-destructive/20 md:text-sm dark:aria-invalid:border-destructive/50 dark:aria-invalid:ring-destructive/40" id="mc_name" autocomplete="off" value="Some value" name="mc_name" /> </div> ThanksExtension slows page even when irrelevant DOM elements are added
Hello! I've noticed that the extension slows down the webapp I'm working on quite a lot even though the vast majority of elements on the page shouldn't be relevant to the extension. The webapp in question involves displaying SVGs with lots of elements (660,000+) inline on the page, and (for various reasons) we start with an more-or-less empty <svg> tag on the page, and then later fill in the contents using `setHTML` or `innerHTML`. When that happens, I can see on a performance profile that there is a long pause caused by the 1Password extension due to (presumably) it inspecting all the inserted elements, even though they are all SVG elements and are thus not relevant to the extension. The length of the slowdown depends on the size of the SVG that's been inserted, but our SVGs are always going to be quite large, since they depict circuit boards, which are multi-layered and can get very complex. At the point that I noticed it, the slowdown was taking more than 43 seconds. (I have a profile exported if it would be useful to the extension devs, but the forums won't let me upload files or post images.) Any chance you could you look into this? I haven't been able to find any way to tell the extension to ignore part of a page, and additionally it seems like the extension should ignore SVG elements by default. Thanks!
Firefox extension autofill broken — InputJsonDeserializationFailed
Since updating to 1Password 8.12.5 on Linux, the autofill feature no longer works in Firefox-based browsers (Firefox and Zen Browser). The same extension version (8.12.4.46) works correctly in Chromium. Copying passwords from the extension popup works fine — only the fill/autofill operation is broken. Environment: OS: Arch Linux (kernel 6.19.6) 1Password app: 8.12.5 (also tested with beta 8.12.6-35 — same issue) 1Password extension: 8.12.4.46 (latest on AMO) Firefox: 148.0 (also tested with 147.0.4 — same issue) Chromium: autofill works with the same extension version and app Steps to reproduce: Open any login page in Firefox Focus on a username/password input field The 1Password inline menu appears and shows matching logins — this works Click on a login to fill — nothing happens Filling via the toolbar popup and keyboard shortcut also does nothing. Copying a password works fine. Error from about:debugging → 1Password → Inspect: Uncaught (in promise) Error: ⛔ Core error code: InputJsonDeserializationFailed sendCoreMessage background.js:108 nextFill background.js:108 What I've tested: Test Result Chromium + same extension + same app Fill works Firefox 148 / 147.0.4 InputJsonDeserializationFailed 1Password beta 8.12.6-35 InputJsonDeserializationFailed X11 instead of Wayland InputJsonDeserializationFailed Copy password from extension Works The Firefox extension's fill request (nextFill → sendCoreMessage) is rejected by BrowserSupport with InputJsonDeserializationFailed. The same extension version works in Chromium, so the issue is in the Firefox-specific fill payload. This is a regression from the 8.12.2 → 8.12.5 app update (downgrading is blocked by database migration).
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.
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.
1P Nightly: getting spammed to download "Apollo Devtools" Chrome Extension!
I've been running 1P Nightly, and currently have v8.12.4.6 installed. Today I went to open my Chrome DevTools console and saw this message: "Download the Apollo DevTools for a better development experience: https://chrome.google.com/webstore/detail/apollo-client-developer-t/jdkknkkbebbapilgoeccciglkfbmbnfm" Which leads to this page for "Apollo Client Devtools" ? I found that link in the 1P Nightly extension's codebase. Why is this prompt appearing? Don't like this at all...
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
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
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".
