W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2011

Re: [DOM3Events] CR

From: Charles Pritchard <chuck@jumis.com>
Date: Sun, 04 Sep 2011 10:27:55 -0700
Message-ID: <4E63B51B.5070105@jumis.com>
To: Doug Schepers <schepers@w3.org>
CC: Anne van Kesteren <annevk@opera.com>, public-webapps <public-webapps@w3.org>, Adrian Bateman <adrianba@microsoft.com>, Jacob Rossi <jrossi@microsoft.com>, Arthur Barstow <art.barstow@nokia.com>, Chaals McCathieNevile <chaals@opera.com>, www-dom@w3.org
On 9/4/11 10:06 AM, Doug Schepers wrote:
> On 9/4/11 12:49 PM, Charles Pritchard wrote:
>>
>> Is there a wiki page or other resource for looking into implementation
>> status on DOM3Events?
>> It's a large spec, and I'd like to plan for it in our internal roadmap.
>
> We will be building a complete test suite and implementation report 
> during CR phase, which is the traditional time that stuff is done.
>
> Informally, I believe that IE9+ implements all of the normative 
> assertions in the DOM3 Events spec (there could be minor details that 
> need better testing), and most of the spec is implemented in other 
> browsers, since much of it is based on existing browser features.
>
> I think the least coverage is in one of the most important features, 
> the keyboard model; I would love to see this implemented in more 
> browsers than just IE, but haven't been able to get anyone to 
> prioritize it yet.  'mouseenter' and 'mouseleave' also need broader 
> support (John Resig was just asking me to expedite this the other day, 
> on behalf of jQuery).

I've got a bad situation with Apple's VoiceOver on Mobile Safari. As 
they have not taken any steps to improve Canvas accessibility, I'm in 
the unfortunate position of only having self-voicing via audio tags.

Is mouseenter and mouseleave intended for touch events as well? On 
Mobile Safari's eyes-free interface, a user simply drags their touch 
across the screen, and as it enters various elements, the elements are 
voiced. The user then double-taps to focus on a given element.

It's a whole-lot-of-work to re-implement that from scratch. mouseenter 
and mouseleave would lessen that burden. But, it is a touch* system, vs 
a mouse* system, at it's core.


>
>
>> I'm no fan of event.pageX, but it's very heavily used in our code base.
>> Our screenX hooks, when written, were targeting Adobe's Flash event
>> namespaces. It's mentioned once, in DOM3Events, in the legacy context of
>> initMouseEvent.
>
> I believe the right place to deal with that is in the CSS Object Model 
> specs.
>

Do you remember which list was discussing the addition of a MouseCoords 
method being available on mouse events? I believe the thought originated 
from the SVG realm.

-Charles
Received on Sunday, 4 September 2011 17:28:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:08 GMT