1Password Oddities

These have been issues for a while, but re-testing them today, I'm using "1Password for Mac 8.11.22 (81122027)", Google Chrome "144.0.7559.59", and 1Password extension "8.11.27.2".

---

Is there a reason why I have to use my mouse and keyboard on web-pages that use XHTML?

https://craig.dev/misc/1Password/2023-12-12-xml/

If I select either the username or password field (I'm using autofocus on the username field, but this isn't necessary)... the 1Password icon appears (good), but if I click on it with the mouse, then it just disappears... so now I need to use the [down arrow] button on my keyboard to show the 1Password account selection menu... but, if I press the [down arrow] a second time (i.e. to make a selection), then the 1Password select menu disappears, so I need to go back to using my mouse to select the account I want.

This seems to be due to the use of `Content-Type: application/xhtml+xml`, you can change back to normal (error tolerant) HTML with the "change" link on this page.

---

Also, because I have a `Permissions-Policy` header on my websites, where I set `ch-ua-high-entropy-values=()` to disable the getHighEntropyValues API, I get this error in the Google Chrome Developer tools:

Permissions policy violation: Collection of high-entropy user-agent client hints is disabled for this document

https://craig.dev/misc/1Password/2026-01-11-high-entropy/ 

---

Also, on either of these pages, you can see the scrolling issue... as in, when you try to scroll the page, the 1Password button remains fixed in position relative to the browsers window (not keeping track of the username/password field location):

I suspect it's related to the setButtonStyles() function in "injected.js", which is using `button.style.position = "fixed"`... I'm not sure on the details, but if I was looking into this, I'd start by considering the use of position absolute.

---

Also, every time I select a username/password field, and then use the down arrow so 1Password opens the select field, I get a warning in the Google Chrome Developer tools:

Added non-passive event listener to a scroll-blocking 'wheel' event. Consider marking event handler as 'passive' to make the page more responsive.

---

And finally, following on with the SMS verification codes discussion, what HTML should I be using on my SMS one-time-code fields, so I can tell 1Password to ignore this field (i.e. so the browser can offer the value from the SMS message)? I'm currently using:

<input name="code" id="sms_code" required="required" autofocus="autofocus" autocomplete="one-time-code" type="text" inputmode="numeric" size="9" maxlength="7" value="">