31–40 of 74 posts
Doesn't seem to be an issue in Firefox, as far as I can tell. Certainly didn't fill any other fields for me.
This seems like an easy fix for the layout engines. Only include a field on autofill if it's currently visible on screen. One might even classify this as a bug.
Browsers really need to support some mechanism where the user can determine precisely what information will be filled prior to it being handed over to the website. This needn't be difficult; Chrome's existing autofill popup already displays a subset of the information, the popup just needs to give a fuller picture.
This seems like an easy fix for the layout engines. Only include a field on autofill if it's currently visible on screen. One might even classify this as a bug.
That's a misuse for the term "autocomplete" in my opinion. What he complains about is "autofill", not "autocomplete" as I understand it. Autocomplete takes the values you used previously and gives you suggestions for the stuff you're typing in yourself. Autofill tries to guess what values are required and fills them in without additional interactions. They're very different mechanisms...
Web devs can recommend input fields not use autocomplete: http://www.w3schools.com/tags/att_input_autocomplete.asp It's considered good practice to use it on login fields, but otherwise depends on whether you think security or user preference should take priority.
Doesn't seem to be an issue in Firefox, as far as I can tell. Certainly didn't fill any other fields for me.
Even if it showed you the fields, it wouldn't be conclusive proof of a privacy leak. Firefox shows links visited without exposing that property outside of render context: https://blog.mozilla.org/security/2010/03/31/plugging-the-cs...
Doesn't seem to be an issue in Firefox, as far as I can tell. Certainly didn't fill any other fields for me.
It's an issue for me with the Lastpass addon in Firefox, if I use the Lastpass autofill. That doesn't make it a Firefox issue, of course.
Earlier quoted context omitted.
Even if it showed you the fields, it wouldn't be conclusive proof of a privacy leak. Firefox shows links visited without exposing that property outside of render context: https://blog.mozilla.org/security/2010/03/31/plugging-the-cs...
The fields in this demo are being echoed back from the server, so if you see values in them then it is indeed proof they are being leaked.
$("#mine").submit( function() {
$("#hide").css("height","auto");