W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: Shadow DOM: events that are stopped

From: Dimitri Glazkov <dglazkov@chromium.org>
Date: Thu, 7 Feb 2013 10:12:04 -0800
Message-ID: <CADh5Ky32Ew03DnvTUi0fL3q4MzBbc-y+85DhO=Qjmi_o6go1zw@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: WebApps WG <public-webapps@w3.org>
On Thu, Feb 7, 2013 at 9:17 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Thu, Feb 7, 2013 at 5:02 PM, Dimitri Glazkov <dglazkov@chromium.org>
> wrote:
> > 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?
> You cannot associate defaults with event types, it's up to who fires
> the event. So it would be up to shadow tree developers and
> specifications that define events that can be dispatched within a
> shadow tree. So if we never want to "leak" load from e.g. <img>,
> <video>, etc. when used in shadow trees, specifications that dispatch
> load would have to set a "scoped to shadow tree flag".

Love it. Energize!

Received on Thursday, 7 February 2013 18:12:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:58 UTC