- From: Hayato Ito <notifications@github.com>
- Date: Thu, 02 Jun 2016 21:28:15 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc:
- Message-ID: <w3c/webcomponents/issues/513@github.com>
We have decided to use `Event.composed` flag (false by default), instead of `Event.scoped`, negating its meaning. See the context: https://github.com/whatwg/html/issues/1160. That means we should have a list of exceptional events whose composed flag should be true, instead of the [current list](http://w3c.github.io/webcomponents/spec/shadow/#scoped-flag). Eventually, instead of having a list in one place, each event's definition should mention its composed flag should be true in each place, but I would like to have a rough consensus here. I have made a list of events, referring UIEvent spec: https://w3c.github.io/uievents/#event-types-list, whose composed flag should be true by default, I think: - Focus Events: blur, focus, focusin, focusout - Mouse Events: click, dblclick, mousedown, mouseenter, mousemove, mosueout, mouseover, mouseup - Wheel Events: wheel - Input Events: beforeinput, input - Keyboard Events: keydown, keyup - Composition Events: compositionstart, compositionupdate, compositionend I am going to update Blink's implementation, however, but what do you think about Composition Events? Should we exclude Composition Events from here? --- 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/513
Received on Friday, 3 June 2016 04:28:47 UTC