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

I took a quick look.

- SD section 2 could probably be moved into a subsection of DOM section 2
- We'd probably create a new top-level section in DOM for shadow DOM. Maybe after "nodes".
- SD sections 3 and 4 would move into the new top-level section.
- SD section 5 would need some work. It needs to be integrated into DOM section 3.
  - "In each algorithm in this section, the Window must be considered as if it were the parent node of the Document so that the Window also receives an event." I am pretty sure HTML has a similar sentence, but I cannot find it easily...
  - UI Events, Touch Events, and HTML will need patches for shadow DOM 5.5-5.9
- SD section 6 mostly gets upstreamed into HTML, some in Editing maybe.
- SD section 7 goes into HTML, creating several new element categories for 7.1, and changing the processing algorithms as in 7.2.
- SD section 8 goes into the new DOM top-level section on shadow DOMs
  - Some of the interface members on `ShadowRoot` need to go into other specs as partial interface definitions: activeElement and styleShets in HTML, element(s)FromPoint in CSSOM, innerHTML in DOM P&S, a few others... I think only host is left, actually.
  - I guess the definition of HTMLSlotElement and assignedSlot go in the HTML spec?
  - The blocklist of elements you cannot attachShadow too goes in HTML, or maybe becomes a DOM concept which HTML references.
- SD section 9 goes into a subsection of the new DOM top-level section on shadow DOMs

We should check with @annevk, but I would be OK with gradually moving over pieces, leaving pointers from the current spec into their new destinations. The trick is figuring out what are good chunks of work to do that in. For example, we could move over the HTMLSlotElement and assignedSlot stuff in one chunk and have it reference the shadow DOM spec until it's fully integrated. We could move over the conceptual stuff in another chunk. Etc.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/377#issuecomment-178834555