Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
joeRinehart
1 month agoNew Contributor
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 ...
- 1 month ago
Hey everyone! I want to thank everyone who called our attention to this and explain what happened and what we’re doing about it.
What happened: Prism.js is a syntax-highlighting library we use for our Labs Snippets feature. While optimizing our build to reduce bundle size, we unintentionally bundled Prism.js into the extension in a way that caused it to run on pages where it shouldn’t, which interfered with code formatting on certain sites. We apologize for the inconvenience this caused.What we’re doing about it: We’ve completed the fix and submitted it to the Chrome Web Store, along with Firefox, Edge, and our other supported extension storefronts. Rollout timing depends on each store’s review process, but we expect it to land over the next few days.
We want to emphasize that vault security was not impacted. At 1Password, protecting our customers’ privacy, passwords, and credentials is our highest priority.
We’ll be publishing a postmortem covering what went wrong, the timeline, and the concrete changes we’re making to how we build and release future browser extension updates.
elbart
30 days agoNew Contributor
1P_Blake Thank for giving us an update here and the explanation. Thanks to the team for taking care of this!
Can you please let us know:
1. Which version numbers contain the fix for the various storefronts?
2. Is the fix already rolled out in the nightly builds?
Thanks and kind regards,
Tim
1P_Blake
Community Manager
27 days agoHey elbart! The fix is included in 1Password for the browser version 8.11.27 and later.
It’s also already rolled out across Nightly, Beta, and Stable builds, so whichever channel you’re on should now have the fix in place! 🙂
- elbart26 days agoNew Contributor
Thanks for letting us now. Fix confirmed on my end.