Re: [w3c/webcomponents] slotchange event should not bubble (#571)

> If it's improper for an event to propagate to ancestor trees of the target's root because exposing that event is potentially 'unsafe' (event name conflicts, carries internal information), then why isn't it also improper for those events to propagate into descendant trees given the contents of those trees are similarly unknown and potentially unsafe for those same events?

The key difference is that the author of a component has a control over what gets used in its shadow tree.  So if it uses another component with its own shadow tree, the outer component's shadow tree is fully aware of that fact.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/571#issuecomment-251260189

Received on Monday, 3 October 2016 23:55:22 UTC