Re: Shadow DOM: events that are stopped

I think this is a nicer solution. Will we have defaults associated with
some types of events or is it completely up to the shadow tree author to
decide the fate of the events?

:DG<


On Thu, Feb 7, 2013 at 5:02 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> Instead of having a fixed list of events that are stopped, maybe
> instead we can pass a flag to the dispatch algorithm with respect to
> whether or not the event being dispatched should exit the shadow
> boundary it started in, if any. That way you can have your own private
> event handling in the shadow tree and for components implemented by
> the user agent they can implement certain user actions as private to
> the shadow tree as well, but if I want I could still dispatch a
> synthetic "scroll" event that goes through the boundary.
>
> Thoughts?
>
> Acknowledgments: Jonas Sicking.
>
>
> --
> http://annevankesteren.nl/
>
>