Re: [w3c/webcomponents] Upstream Shadow DOM spec to DOM/HTML Standard (#377)

Regarding TouchEvents, it looks what I have done is to make TouchEvents 'composed' events, and add event retargeting process.
- https://github.com/w3c/touch-events/commit/eeed53b305bc1c1fa35f7280aef342f16ebb230c
- https://github.com/w3c/touch-events/commit/5999f2752a56980ac2676e29a9d54bde08ec20d9

Regarding UIEvents, it looks what I have done is to make some UIEvents 'composed' events.
- https://github.com/w3c/uievents/commit/734123812b2b941ff0a7ace29490317d17bd05ae
- https://github.com/w3c/uievents/commit/d075314393fad8e07af797dbbab9a5dcfe11ee16

Hmm, I forgot to add retargeting process there. :(

Regarding https://github.com/w3c/DOM-Parsing/issues/21, this was not fixed. I remember that we had a discussion about whether we should add innerHTML to DocumentFragment, rather than ShadowRoot, or not. However, I guess that was not solved due to the lack of follow-up.

> Should we perhaps create a new tracking issue for all these items so we have a clean slate for all upstream work?

Yes, that would be great. Recently, I couldn't spend much time on upstreaming tasks. Please feel free to create a new tracking issue.

-- 
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/377#issuecomment-327076086