- From: Hayato Ito <notifications@github.com>
- Date: Tue, 20 Sep 2016 04:03:15 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Tuesday, 20 September 2016 11:03:53 UTC
Blink has already shipped `slotchange` events. It might be difficult to change the behavior significantly. I think making it to non-bubble events is fine in Blink. The compatibility risk is low enough, I guess. BTW, I'm curious that what's criteria in general to decide a bubble or non-bubble for an event? It looks there is always a use case where bubbling might be useful for web developers, I guess. Isn't it true? Even if we adopt a bubble event here, users can ignore *non-essential* events by checking "event.currentTarget != event.target" in general. -- 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-248270245
Received on Tuesday, 20 September 2016 11:03:53 UTC