W3C home > Mailing lists > Public > www-archive@w3.org > May 2014

Re: apparent acc bug in firefox

From: Marco Zehe <marco.zehe@googlemail.com>
Date: Sat, 10 May 2014 12:06:55 +0200
Message-ID: <536DFA3F.6020300@googlemail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>, Alexander Surkov <surkov.alexander@gmail.com>, David Bolter <david.bolter@gmail.com>
CC: www-archive <www-archive@w3.org>
Hi Steve,

that is exactly what Firefox does, and purposely so. There have been so 
many web sites out in the wild which had buttons and other stuff react 
to mousedown or mouseup only that we were requested to expose mousedown 
and mouseup as click actions in addition to onclick, since it was 
assumed that these were items whose programmers only allowed mouse 
clicks, but no keyboard input. You know, clickable divs and spans.

I believe even Gmail had this for a long long time, and they were one of 
the reasons we did it this way, to give an indication that these items 
can be interacted with via the mouse.

So: It's not a bug, it's a feature! And the reason is the world wild west.

And why exactly did they register a mousedown event on a non-interactive 


Am 10.05.2014 10:49, schrieb Steve Faulkner:
> hi gang,
> I have been trying to resolve an issue with custom elements developed 
> using the polymer library.
> It appears that Firefox exposes a mousedown event listener as a click 
> default action in acc layer.
> This results in non interactive custom elements being announced as 
> clickable.
> can you have a look at this message to the polymer list to see if you 
> can shed any light?
> https://groups.google.com/d/msg/polymer-dev/4ObaAH29S08/NiBUPOmfiawJ
> correct link to example: http://jsbin.com/vegam/1/quiet
> thanks!
> --
> Regards
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
Received on Saturday, 10 May 2014 10:07:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:34:58 UTC