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.
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
Console flooded with errors when clicking links during 1Password passkey selection dialog
Hi, I’m experiencing an issue with the 1Password browser extension when testing WebAuthn API integration on my own website. Environment macOS Chrome (latest version) 1Password browser extension Issue I’ve successfully implemented WebAuthn API functionality for login on my website. However, the 1Password extension behaves unexpectedly: When the 1Password passkey selection dialog is open, if I click a link on the page, the page transition happens, but the Chrome DevTools console gets flooded with a large number of log, warn, and error messages. This feels like a bug. Steps to Reproduce Register a passkey in 1Password for the test site. Open the login page, which triggers the 1Password passkey selection dialog. While the dialog is open, click any link on the page. The navigation works, but the console outputs a large number of log, warn, and error messages. Expected Behavior Page navigation should happen without producing unnecessary console output. Actual Behavior Console is flooded with log, warn, and error messages. Additional Information I will attach/paste the console output below for reference. background.js:80 📤 Sending <NmLockState> message to native core <740716061> background.js:80 📥 Received message <NmLockState> from native core <740716061>. Duration: 4.8ms background.js:80 DeviceTrust: access denied: [ missing backoffice permission, missing admin permission ] - aborting （anonymous） @ background.js:80 background.js:80 📤 Sending <NmOfflineStatus> message to native core <3907478951> background.js:80 📥 Received message <NmOfflineStatus> from native core <3907478951>. Duration: 1.7ms background.js:80 Could not complete _handleGetCredential: disconnected （anonymous） @ background.js:80 background.js:80 📤 Sending <NmLockState> message to native core <3923595490> background.js:80 📥 Received message <NmLockState> from native core <3923595490>. Duration: 4.1ms background.js:80 📤 Sending <NmLockState> message to native core <2088568031> background.js:80 📥 Received message <NmLockState> from native core <2088568031>. Duration: 4.3ms background.js:80 📤 Sending <NmLockState> message to native core <780253718> background.js:80 📥 Received message <NmLockState> from native core <780253718>. Duration: 4ms background.js:80 📤 Sending <NmLockState> message to native core <3199044829> background.js:80 📥 Received message <NmLockState> from native core <3199044829>. Duration: 3.8ms background.js:80 📤 Sending <NmOfflineStatus> message to native core <469136938> background.js:80 📥 Received message <NmOfflineStatus> from native core <469136938>. Duration: 6ms background.js:80 Loaded page details in 2 ms. background.js:80 Analyzed the page in 0.4000000059604645 ms. background.js:80 📤 Sending <NmOfflineStatus> message to native core <2269321457> background.js:80 📥 Received message <NmOfflineStatus> from native core <2269321457>. Duration: 3.3ms background.js:80 [popup] Not attempting to connect to desktop app: already connected or connecting to desktop app background.js:80 Decided not to attempt reconnection to the desktop app. background.js:80 📤 Sending <NmLockState> message to native core <2789903974> background.js:80 📥 Received message <NmLockState> from native core <2789903974>. Duration: 2.7ms background.js:80 DeviceTrust: access denied: [ missing backoffice permission, missing admin permission ] - aborting （anonymous） @ background.js:80 background.js:80 📤 Sending <NmOfflineStatus> message to native core <3819754395> background.js:80 📥 Received message <NmOfflineStatus> from native core <3819754395>. Duration: 3.6ms background.js:80 📤 Sending <NmLockState> message to native core <1861163921> background.js:80 📥 Received message <NmLockState> from native core <1861163921>. Duration: 3.1ms background.js:80 📤 Sending <NmLockState> message to native core <2199877840> background.js:80 📥 Received message <NmLockState> from native core <2199877840>. Duration: 4ms background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 background.js:80 📥 Sync started for account xxxxxxxx - syncing all background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 background.js:80 Managed Apps - Feature flag is NOT enabled background.js:80 ✅ Sync completed for account xxxxxxxx - took 969ms background.js:80 📤 Sending <NmOfflineStatus> message to native core <335039426> background.js:80 📥 Received message <NmOfflineStatus> from native core <335039426>. Duration: 8.1ms background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 background.js:80 📥 Sync started for account xxxxxxxx - syncing all background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 background.js:80 Managed Apps - Feature flag is NOT enabled ✅ Sync completed for account xxxxxxxx - took 935ms 📤 Sending <NmOfflineStatus> message to native core <228318852> 📥 Received message <NmOfflineStatus> from native core <228318852>. Duration: 1.9ms Failed to refresh keysets <redacted> （anonymous） @ background.js:80 📥 Sync started for account xxxxxxxx - syncing all Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 📤 Sending <NmLockState> message to native core <3763395867> 📥 Received message <NmLockState> from native core <3763395867>. Duration: 3.1ms Managed Apps - Feature flag is NOT enabled ✅ Sync completed for account xxxxxxxx - took 900ms 📤 Sending <NmOfflineStatus> message to native core <527828929> 📥 Received message <NmOfflineStatus> from native core <527828929>. Duration: 3.3ms Could not complete _handleGetCredential: disconnected （anonymous） @ background.js:80 DeviceTrust: access denied: [ missing backoffice permission, missing admin permission ] - aborting （anonymous） @ background.js:80 📤 Sending <NmOfflineStatus> message to native core <3893879316> 📥 Received message <NmOfflineStatus> from native core <3893879316>. Duration: 1.7ms 📤 Sending <NmLockState> message to native core <2484059834> 📥 Received message <NmLockState> from native core <2484059834>. Duration: 4.3ms 📤 Sending <NmLockState> message to native core <567699292> 📥 Received message <NmLockState> from native core <567699292>. Duration: 3.8ms 📤 Sending <NmLockState> message to native core <2496790293> 📥 Received message <NmLockState> from native core <2496790293>. Duration: 3.6ms Failed to refresh keysets <redacted> （anonymous） @ background.js:80 📥 Sync started for account xxxxxxxx - syncing all Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Managed Apps - Feature flag is NOT enabled ✅ Sync completed for account xxxxxxxx - took 1264ms 📤 Sending <NmOfflineStatus> message to native core <2459928279> 📥 Received message <NmOfflineStatus> from native core <2459928279>. Duration: 3.1ms Failed to refresh keysets <redacted> （anonymous） @ background.js:80 📥 Sync started for account xxxxxxxx - syncing all Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Managed Apps - Feature flag is NOT enabled ✅ Sync completed for account xxxxxxxx - took 891ms 📤 Sending <NmOfflineStatus> message to native core <346739443> 📥 Received message <NmOfflineStatus> from native core <346739443>. Duration: 4.3ms 📤 Sending <NmLockState> message to native core <1926301438> 📥 Received message <NmLockState> from native core <1926301438>. Duration: 3.9ms Failed to refresh keysets <redacted> （anonymous） @ background.js:80 📥 Sync started for account xxxxxxxx - syncing all Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Managed Apps - Feature flag is NOT enabled ✅ Sync completed for account xxxxxxxx - took 974ms 📤 Sending <NmOfflineStatus> message to native core <4246935782> 📥 Received message <NmOfflineStatus> from native core <4246935782>. Duration: 3.7ms Failed to refresh keysets <redacted> （anonymous） @ background.js:80 📥 Sync started for account xxxxxxxx - syncing all Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Managed Apps - Feature flag is NOT enabled ✅ Sync completed for account xxxxxxxx - took 871ms 📤 Sending <NmOfflineStatus> message to native core <969923831> 📥 Received message <NmOfflineStatus> from native core <969923831>. Duration: 3.2ms 📤 Sending <NmLockState> message to native core <2384356258> 📥 Received message <NmLockState> from native core <2384356258>. Duration: 4.1ms Failed to refresh keysets <redacted> （anonymous） @ background.js:80 📥 Sync started for account xxxxxxxx - syncing all Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Failed to refresh keysets <redacted> （anonymous） @ background.js:80 Managed Apps - Feature flag is NOT enabled ✅ Sync completed for account xxxxxxxx - took 865ms 📤 Sending <NmOfflineStatus> message to native core <1380548022> 📥 Received message <NmOfflineStatus> from native core <1380548022>. Duration: 1.7ms 📤 Sending <NmLockState> message to native core <2946571035> 📥 Received message <NmLockState> from native core <2946571035>. Duration: 3.1ms 📤 Sending <NmLockState> message to native core <2259480419> 📥 Received message <NmLockState> from native core <2259480419>. Duration: 2.4ms 📤 Sending <NmLockState> message to native core <2244117207> 📥 Received message <NmLockState> from native core <2244117207>. Duration: 4ms Could not complete _handleGetCredential: disconnectedConfirm Password Forms
We have a "sudo mode" form similar to GitHub which requires confirming your password for sensitive actions: I have several accounts. I'm trying to tell 1Password which password to use. I have followed the instructions here: https://developer.1password.com/docs/web/compatible-website-design#password-change-and-reset-forms And added a hidden username field: But this doesn't seem to help. If I un-hide the username then if I select the username field it offers to fill the right account. But if I select the password field it just displays all accounts again. How can I tell 1Password which account to use in this form? Apologies if this has already been asked and answered. I have done my best to search and came up empty.
Save one-time password prompt
Hi, When setting up TOPT using the default Keycloak v26.3.0 theme I get prompted to save the OTP in 1password. Really like and appreciate this. I lose the save OTP popup when using a custom keycloakify theme. Thought maybe had something to do with my customizations. Setup a brand new keycloakify project and same result. How does 1password detect that there is OTP configuration? Anything I can do to influence 1password to display the save OTP popup? Thank you for the great product.
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
