I never really loved how extensions have to put their interfaces in the website's DOM if they want to be able to work with the page's elements, like this selector, or a password manager's suggested logins. Especially in the password manager's scenario, it could leak what accounts you have to a given website to that website itself, if the page is looking for new DOM elements. Not exactly a showstopper vulnerability, but it's not a good thing.
This leak doesn’t exist. The injection goes in a sandboxed iframe, which is protected from the rest of the page by the same security boundary that prevents them from puppeteering your bank’s pages in an iframe they’ve embedded themselves.
Did XUL extensions in Firefox prior to WebExtensions have a different way of interacting with the page contents? I know they tended to integrate better with the host browser's UI and inherited more of the host OS's UI conventions as a result, but the web back then didn't require as many CSS-based ad blocking rules (domain/URL-based rules worked for almost everything) so I don't remember what the element picker UI was like on eg. AdBlock Plus or Adblock 0.5.
In the case of password managers, amy decent one will put their DOM elements in a closed shadowDOM root, which prevents the page scripts from interacting with it entirely.
Setting aside data leaks, this also causes bugs in extensions to potentially affect websites en masse. For instance, as recently as this January, 1Password began injecting prism.js globally on all pages, breaking many <code> blocks for at least 20 days: https://mjtsai.com/blog/2026/01/07/1password-browser-extensi...