Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
brianoflondon
1 month agoNew Contributor
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...
- 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.
1P_Blake
Community Manager
19 days agoHey 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.
luckman212
18 days agoFrequent Contributor
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.
- luckman21212 days agoFrequent Contributor
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?
- brianoflondon11 days agoNew Contributor
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.
- 1P_Blake12 days ago
Community Manager
Hey luckman212! Thanks for circling back here, and sorry for the delayed reply here on my behalf.
While I don’t have a concrete ETA I can share yet for when this fix will move from Nightly into the stable track, the plan is definitely still to roll it through beta and then production once we’re confident it’s behaving well across different setups.
Totally understand wanting to stick with stable given your scripts and workflows, but I’m really glad to hear you jumped into Nightly and that things are working again.
Also, thanks for calling out the feedback on the floating Sign In notification! This kind of input is exactly what we like hearing while changes like this are still relatively fresh. I can’t promise a toggle or specific behavior, but this feedback is definitely being seen by the team.
- luckman21211 days agoFrequent Contributor
Ok, I opened a separate thread about that here: Nightly: please be friendly to keyboard users! | 1Password Community
- AdamKski12 days agoNew Contributor
Unfortunate = extremely slow. Still waiting for the Android Chrome update.
The floating bubble seems unnecessary to me too.
- WackyWRZ12 days agoNew Contributor
I fully agree that the response to this has been unacceptably slow... This has been an issue for well over a month now. Furthermore, outside of the slow fix - the lack of communication from 1P is even more concerning.
To make it even more annoying, this broke right in the midst of my annual renewal, and because of holidays I didn't have time to do testing and migration to a different password manager. Had I known something like this would have taken so long, I would have dedicated time to testing alternatives. The (lack of) response to this will certainly make me re-evaluate them.
As an aside I actually DO like the new floating bubble. It works much more consistently for me than the old way. That being said, it shouldn't be that hard to have a toggle in settings to turn it on/off... But adding that toggle feature may take another 2 months at this rate.