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

Re: review of section 6

From: Al Gilman <asgilman@iamdigex.net>
Date: Sat, 06 Mar 1999 20:17:41 -0500
Message-Id: <199903070114.UAA1647953@relay.interim.iamworld.net>
To: Ian Jacobs <ij@w3.org>, Charles McCathieNevile <charles@w3.org>
Cc: WAI UA group <w3c-wai-ua@w3.org>
At 03:01 PM 3/6/99 -0500, Ian Jacobs wrote:
>
>>Should it apply to navigating the children of an element which
>>   handles bubbled events? I suspect so. 

>
>I'm not sure. That's why the checkpoint refers to "associated
>event handlers", which in HTML will mean "on*" attributes. I don't
>think the WG has enough information yet from the DOM to say more.

I suspect not.  In the classic pathological case where the script reads the
mouse position and does different things based on where the mouse was,
there is nothing in the paramter profile which says the mouse position
dependency lines up with the layout boundaries of elements in the document
tree.  So I am afraid that it is like a server-side image map.  One should
be able to navigate to the element for which an on* event is bound to a
handler, but not necessarily wander the tree inside that element.  That is
just too many places to go.  Unless you are going to slave a pseudo-mouse
position to the layout geometry associated with the elements navigated to
in the parse tree, the navigation does not tell the script anything that
calling the script from the enclosing element (where it is mentioned) fails
to tell it.

>> All Children? Harder to say.
>>
 
Al
Received on Saturday, 6 March 1999 20:14:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:48:49 GMT