Re: [webcomponents] Changes to Dispatching Events (#274)

> E.g. if <img> starts dispatching a new event tralala we wouldn't want to update shadow DOM (and perhaps create issues for some other element that doesn't want a scoped tralala event). <img> should just say it's a scoped event.

I think I tried the wording to resolve the concern; i.e., it says "The following events are the scoped events, but **not limited to**", so the new spec simply can say "the new event `tralala` is a scoped event" without updating Shadow DOM spec (or DOM if this is upstreamed by then.)

If it doesn't read so, maybe my English problem, but I'm suspecting that I'm not understanding your intention very well rather than poor English in this case.

What I don't understand is, if we don't patch DOM spec, and don't list up event types to set the `scoped flag` to true by default, how do I specify which existing events are the scoped events?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/pull/274#issuecomment-120071795