Autofill no longer works on HTTP pages; iOS shows white blank screen

I’m running into an issue where 1Password can’t fill on any http:// pages across multiple platforms, and on iOS it can even result in a white/blank screen when I try to fill.

What’s happening

• iOS (1Password app + Safari extension): On http:// pages, 1Password cannot autofill. When I invoke 1Password to fill on an HTTP page, the 1Password UI becomes a white/blank screen.
• Chrome / Edge extension (desktop): Autofill does not work on http:// pages at all.
• macOS app / Safari (macOS): Same behavior — no filling on http:// pages.

Expected behavior

I understand HTTP is insecure, but I still expect either:

1. autofill to work (possibly with a warning/confirmation), or
2. a clear message explaining that filling is blocked on http:// pages — not a blank/white screen on iOS.

Notes / why this matters

These http:// sites are mostly local network / self-hosted services that don’t have HTTPS enabled yet (or are reachable only via LAN IP/hostnames). So “just use HTTPS” isn’t always possible.

Also, I saw other reports that HTTP filling stopped working recently in some extension versions (people mentioned it worked again after downgrading), so I’m wondering if this is a regression. 1password.community

Steps to reproduce (iOS)

1. Open Safari on iOS and go to an http:// login page (example: http://[local-address]/login).
2. Tap into the username/password field and try to fill with 1Password (AutoFill or Safari extension pop-up).
3. Result: no autofill; in some cases the 1Password UI turns into a white/blank screen.

My environment

• iOS: 26.2
• 1Password for iOS: 8.11.22
• macOS: 26.2
• 1Password for macOS: 8.11.22
• Browser: Chrome 143.0.7499.170 / Edge 143.0.3650.96 / Safari 26.2 (21623.1.14.11.9)
• 1Password browser extension: Chrome/Edge 8.11.27.2、Safari 8.11.22.27

What I’ve tried

• Restarted browser(s) and device(s)
• Updated 1Password apps and extensions
• Re-enabled / reinstalled the extension(s)
• Confirmed the Login item is correctly associated with the site

Could you confirm whether filling on http:// pages is supposed to be blocked now, and if not, whether this is a known bug/regression?
If you need diagnostics/logs, tell me what to collect and where to send them.