- From: Jim Ley <jim@jibbering.com>
- Date: Fri, 4 Jan 2002 20:41:29 -0000
- 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 desirable. > That is why UAAG only requires > activation of events associated with explicit event handlers of an > element I feel this is an oversight... Jim.
Received on Friday, 4 January 2002 15:43:08 UTC