On Wed, Mar 30, 2016 at 9:31 AM, Joseph Scheuhammer <clown@alum.mit.edu>
wrote:
> On 2016-03-29 6:00 PM, Alexander Surkov wrote:
> > Hi, Rich. I'm not completely sure what you mean.
>
> Maybe this will clear it up: in an earlier email, you wrote:
>
> > If you put an input element under a body with onclick, then I think it
> > won't pick up the body's action.
>
> I took that to mean that clicking on the <input> would not invoke the
> body's onclick handler. I tested it and it does invoke the body's
> onclick handler.
I was talking about accessibility layer only. If you mean DOM events, then
it's probably correct behavior as events should be bubbling.
> In order to avoid that handler, you need to add a
> click listener to the <input> element itself that calls the event's
> stopPropagation() method.
>
I'm still confused. Do you mean the accessibility layer should add DOM
events listeners?
>
> Then again, maybe that's not what you meant by your comment about input
> elements. What did you mean? :-)
>
I meant that an accessible object for input element shouldn't expose
'click' action of a document accessible, which is picked up from HTML:body
click listener.
>
> --
> ;;;;joseph.
>
> 'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
> - C. Carter -
>
>