On Wed, Dec 3, 2014 at 12:26 PM, Igor Minar wrote:
> In FF 34 the form autofill works well but
> password autofill doesn't fire any events.
Do you have a testcase demonstrating this problem? Based on my
knowledge of Firefox code, I am surprised that there would be a
difference between password an
Just to follow up on this for archival purposes...
In Chrome M40 (possible even sooner) the proper input and change events are
triggered for both form and password autofill. Good job guys!
Safari 7 and 8 are still broken. In FF 34 the form autofill works well but
password autofill doesn't fire an
On 2014-11-14 19:10, Evan Stade wrote:
The problem is that we don't think autocomplete="off" is used judiciously.
Could you make a compromise and respect autocomplete="off" for only
type="text", and ignore autocomplete="off" for all other input types as
you guys planned?
And then look at how
On Thu, Nov 13, 2014 at 11:42 PM, Roger Hågensen wrote:
> On 2014-11-14 08:02, Evan Stade wrote:
>
>> On Thu, Nov 13, 2014 at 5:17 PM, Roger Hågensen
>> wrote:
>>
>> On 2014-11-13 20:20, Evan Stade wrote:
>>>
>>> Currently this new behavior is available behind a flag. We will soon be
inve
I believe so, but I'll double check and will email you off this thread.
\i
On Thu Nov 13 2014 at 11:06:37 PM Evan Stade wrote:
> That sounds like crbug.com/354257 which was fixed in March. Are you sure
> this is still a problem on newer versions of Chrome?
>
> On Thu, Nov 13, 2014 at 8:22 PM, I
On 2014-11-14 08:02, Evan Stade wrote:
On Thu, Nov 13, 2014 at 5:17 PM, Roger Hågensen wrote:
On 2014-11-13 20:20, Evan Stade wrote:
Currently this new behavior is available behind a flag. We will soon be
inverting the flag, so you have to opt into respecting autocomplete="off".
I don't l
On 2014-11-13 20:20, Evan Stade wrote:
Chrome already ignores the prevalent autocomplete="off" for password
fields. We plan to ignore this tag for Autofill (addresses, credit cards)
fields as well. autocomplete="off" will still be respected for autocomplete
data (e.g. past searches on crbug.com).
That sounds like crbug.com/354257 which was fixed in March. Are you sure
this is still a problem on newer versions of Chrome?
On Thu, Nov 13, 2014 at 8:22 PM, Igor Minar wrote:
> Are you going to properly fire change&input events when autofill happens?
>
> The current autofill behavior is causin
On Thu, Nov 13, 2014 at 5:17 PM, Roger Hågensen wrote:
> On 2014-11-13 20:20, Evan Stade wrote:
>
>> Currently this new behavior is available behind a flag. We will soon be
>> inverting the flag, so you have to opt into respecting autocomplete="off".
>>
>>
> I don't like that browsers ignore HTML
On 2014-11-14 06:12, Peter Kasting wrote:
On Thu, Nov 13, 2014 at 9:03 PM, Roger Hågensen wrote:
This is getting more off topic but... have you ever typed wrong and now
the autocomplete keeps listing your wrong spelling every time? And the only
way to fix it is to nuke all your data, there is
On Thu, Nov 13, 2014 at 9:03 PM, Roger Hågensen wrote:
> This is getting more off topic but... have you ever typed wrong and now
> the autocomplete keeps listing your wrong spelling every time? And the only
> way to fix it is to nuke all your data, there is no way to edit/control the
> auto sugge
On 2014-11-14 04:30, Glenn Maynard wrote:
(Trimming for time and to avoid exploding the thread. Others can
respond to the rest if they like.)
No it's inherently correct for the use case as listeners tend to
enter things like:
"Could you play Gun's'Rose?"
"Love you show, more
Are you going to properly fire change&input events when autofill happens?
The current autofill behavior is causing major headaches for application
and framework developers and by ignoring autocomplete attribute you disable
the only way developers can work around this bug.
On angular we had to dev
(Trimming for time and to avoid exploding the thread. Others can respond
to the rest if they like.)
On Thu, Nov 13, 2014 at 8:26 PM, Roger Hågensen wrote:
> Punishing those who do it right because of the stupidity of the many,
> can't say I'm too thrilled about that.
Leaving it in is punishin
On 2014-11-14 03:57, Ben Maurer wrote:
If the site sets autocomplete=off could you disable the saving of new
suggestions? One of the main use cases for turning off autocomplete is to
disable the saving of sensitive or irrelevant information. If the user is
filling in an address or cc num it's
On 2014-11-14 02:49, Glenn Maynard wrote:
Unfortunately, even if a couple pages have a legitimate use for a
feature, when countless thousands of pages abuse it, the feature needs
to go. The damage to people's day-to-day experience outweighs any
benefits by orders of magnitude.
Also, banks ge
If the site sets autocomplete=off could you disable the saving of new
suggestions? One of the main use cases for turning off autocomplete is to
disable the saving of sensitive or irrelevant information. If the user is
filling in an address or cc num it's likely they have the opportunity to save
On 2014-11-14 02:49, Glenn Maynard wrote:
On Thu, Nov 13, 2014 at 7:17 PM, Roger Hågensen wrote:
I have one real live use case that would be affected by this.
http://player.gridstream.org/request/
Unfortunately, even if a couple pages have a legitimate use for a feature,
when countless thous
On Thu, Nov 13, 2014 at 7:17 PM, Roger Hågensen wrote:
> On 2014-11-13 20:20, Evan Stade wrote:
>
>> Currently this new behavior is available behind a flag. We will soon be
>> inverting the flag, so you have to opt into respecting autocomplete="off".
>>
>>
> I don't like that browsers ignore HTML
On 2014-11-13 20:20, Evan Stade wrote:
Currently this new behavior is available behind a flag. We will soon be
inverting the flag, so you have to opt into respecting autocomplete="off".
I don't like that browsers ignore HTML functionality hints like that.
I have one real live use case that wo
Hi,
Chrome already ignores the prevalent autocomplete="off" for password
fields. We plan to ignore this tag for Autofill (addresses, credit cards)
fields as well. autocomplete="off" will still be respected for autocomplete
data (e.g. past searches on crbug.com).
We think this will break a very sm
21 matches
Mail list logo
