Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
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...
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.
1P_Blake
Community Manager
Community ManagerHey 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.
Glad to see this fix is working! I prefer not to switch release tracks because I have quite a few scripts and other things tied to 1Password that I don't want to disrupt. Could we get an idea of how far out the 1Password team expects before this fix is pushed to the stable track? If it's only a few days away then I'd like to wait.
Well, since there was no reply I got tired of waiting. I installed Chrome Nightly v8.12.2.4. HTTP fill is working again.
Not a fan of the new floating Sign In notification- I used to be able to keep my hands on the keyboard and just hit e.g. down arrow, <ENTER> to sign into a site. Now I have to reach for the mouse which is slower.
The response to this has been pretty unfortunate. Is everything ok at AgileBits?
The keyboard shortcut to show fill in options with the down arrow hasn't stopped working. The bubble doesn't change that if you're just using the keyboard.
Also tested the nightly in Arc browser(Chrome based) and it's working like a charm on my local hosted custom dns http service
Yup the nightly has fixed it for me on MSEdge, also like the popup as well
This seems to fix it for me on Brave.
The new log in thing at the top is also much better than prior interfaces.Currently running 8.12.0.3 nightly on Edge. Can confirm that the autofill is now working on localhosts / http across my internal network.
Also really like the popup that happens on this version for autofill across the board!
Is there a way to test this with Safari?
For what it's worth, I did try the nightly extension for Firefox and it did present the 1P dialog for an http://192.168.x.x local connection.
However, I don't use FF regularly so I can really watch for anything "weird". Thus my comment regarding Safari testing.
I don't mean to be having a conversation with myself here but I see the Safari beta extension is distributed under TestFlight, so I assume that is why there is a limitation for distributing a Nightly. That said, if I install the TestFlight beta version it's not clear I'll get any indication that it has made its way into the beta other than to see it start appearing.
They really should be providing a little more detailed TestFlight release notes than "We've made general improvements and fixed various bugs for a better 1Password experience". <eye roll>
