Open huonw opened 3 years ago
Still a bug in Firefox 38.1
what is the rationale behind disabling autofill in private browsing mode? It seems to me that the two are completely unrelated.
Furthermore, the consequences on usability of disabling autofill on devices which lack a physical keyboard are very important.
It is 2022 and it is still not fixed. A privacy feature no less.
Still not fixed
There's some sites that I prefer to only log into in private browsing, like Facebook. It seems like private browsing completely disables autofill, and this ends up being annoying. This also applies to other use-cases where autofill may fail, e.g. saved private info that aren't strictly passwords, or websites with poor login forms.
Potentially related issues: #8371, #8479.
(Thanks for Firefox for iOS :+1: )
Steps to reproduce
(Sorry for no video, but I don't feel comfortable revealing my accounts.)
Setup:
Now, try to fill in the password:
This is 16 taps, and it's pretty fiddly.
Expected behavior
It'd be great if this process was smoother. There's potentially several options off the top of my head (and potentially several apply):
Actual behavior
It takes quite a while to log into any website where copying username/password are required. This makes me less likely to use private browsing and default to, say, being logged into Facebook in non-private-browsing (my typical interaction is logging in to check if I have any notifications, and I now spend more time logging in than doing that task).
Device & build information
┆Issue is synchronized with this Jira Task