Re: Native Password AutoFill Extension macOS

Today's status update highlights one more reason 1Password developers need to prioritize Safari Native Autofill on MacOS:

1Password Browser Extension Code Syntax Rendering Issue

Jan 23, 2026 at 12:04 PM

Resolved - The 1Password browser extension, which works by injecting code into web pages, inadvertently included code from PrismJS, a third party dependency, breaking syntax highlighting on some websites that display code blocks.

I do not want an extension injecting unnecessary Javascript into every web page I visit, and certainly not inadequately tested 3rd party Javascript. The next time this happens, the third party code could inject a security vulnerability, and not just a formatting issue. Surely a security focused company should understand why this is an issue. And yes, I know about Universal Autofill, and I don't want to give 1Password accessibility permissions either. Why does a security focused company have so much trouble understanding the https://en.wikipedia.org/wiki/Principle_of_least_privilege?

As a bonus, support for Safari Native Autofill on MacOS will give a far better user experience. I'm not even going to get started on the frustrations created by the UI of the 1Password Safari extension.