* Anne van Kesteren 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.
Such behavioral oddities would have to be exposed on the event objects anyway because authors would otherwise have a hard time debugging this, much like event objects expose whether they bubble. I assume the current list is only a band-aid for discussion. -- Björn Höhrmann · mailto:bjo...@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/