W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2002

Re: Next events meeting: 17 Jan 2002 @ 4pm ET

From: Jim Ley <jim@jibbering.com>
Date: Fri, 4 Jan 2002 20:41:29 -0000
Message-ID: <001301c19560$351433c0$ca969dc3@emedia.co.uk>
To: <w3c-wai-ua@w3.org>
"Jon Gunderson":
> A mousedown attached to the body element is usually useless (from an
> accessibility perspective) since any element in the document can
respond to
> it.

I see no problems with this, consider a page which allows you to annotate
any element on it, you need a mechanism to specify which element you are
annotating - "Mousedown on the element you wish to annotate." the
element(/node) that fired the event is then obtained and used in the
annotation, from a script perspective you only capture after it's bubbled
to the body, it's inefficient to capture anywhere else.

So in this instance, a UA needs to fire a mousedown on any child element
of the element which actually has the handler, I see no problems of doing
the annotation in a voice or other non mouse browser.  I do see that so
as to make a user aware that they can fire onmousedown sensibly, whether
the event is defined on the element/node or one its ancestors is

> That is why UAAG only requires
> activation of events associated with explicit event handlers of an
> element

I feel this is an oversight...

Received on Friday, 4 January 2002 15:43:08 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:31 UTC