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 &lt;code&gt; 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