Forum Discussion

brianoflondon's avatar
brianoflondon
New Contributor
1 month ago
Solved

Has something changed: http:// not filling in any more?

For passwords I have that are specifically http:// like on my own Lan, these aren't being suggested any more by 1Password extension in Brave. Anything https:// is working. And yes I have http:// s...
browser extension
  • 1P_Blake's avatar
    1P_Blake
    19 days ago

    Hey everyone! đź‘‹

    We’re testing a fix for HTTP filling, including non-HTTPS localhost setups. That fix is already live in the nightly version of the browser extension, and assuming things look good, we’ll roll it into beta and then production next. For now, the workaround is still to copy and paste or drag and drop your credentials.

    If you’re willing to help us test, you can grab the nightly builds here (there is no nightly version for Safari): Use 1Password beta or nightly releases

    Appreciate everyone’s patience here. If you try the nightly and notice anything weird, definitely give us a shout here in the thread.

UrsaBear's avatar
UrsaBear
New Contributor
1 month ago

Based on my observation, it is likely that the 8.11.22 version of the browser extension in the Edge extension store introduced the use of the window.crypto.randomUUID method.

However, the window.crypto methods can only be used in localhost and HTTPS environments (See: https://developer.mozilla.org/en-US/docs/Web/API/Crypto/randomUUID). In HTTP environments, it reports the error “window.crypto.randomUUID is not a function”, which causes the auto-fill feature to fail.

 

Currently, I have switched to version 8.11.20.39 from the Chrome extension store, and it is still working fine.

passion_to_live's avatar
passion_to_live
New Contributor
1 month ago

i alse installed older version:8.11.18.36 that autofill works well for me, but when i reopen chrome for updating, the 1P extension will auto update to latest version, and autofill fail works again.... and i re install 1P ex older version .....