2022 Appendix Backlog

[thescientist13]

Per #43 , just wanted to track all the items in the Appendix we would like to capture for our report in one place, that we can check off as they get added.

Discussions for all these are happening in #31

1. 🌟 Form-Associated Custom Elements - feat: add form-associated custom elements content #42
2. 🌟 Cross-root ARIA - Add Cross Root Aria status #46
3. 🌟 Constructable Stylesheets & adoptedStyleSheets - Constructable Stylesheets #50
4. 🌟 CSS Module Scripts - CSS Modules #58
5. 🌟 Scoped Element Registries - Add scoped custom element registries #51
6. 🌟 Declarative Shadow DOM - added declarative shadow DOM #45
7. Composed Selection
8. Declarative CSS Modules
9. Children changed callback - Add the section for children changed callback in 2022 #40
10. Open styling of shadow roots
11. Declarative custom elements - docs: add API report update for declarative elements, lazy elements, DOM parts, and custom attributes #41
12. 🚫 Theming - Themeing #54
13. Styling children of slotted content
14. Custom CSS State - CustomStateSet #56
15. 🌟 Imperative Slot Assignment - Imperative Slot Assignment #55
16. 🚫 CSS Properties and values inside shadow root
17. Lazy custom element definitions - docs: add API report update for declarative elements, lazy elements, DOM parts, and custom attributes #41
18. DOM Parts - docs: add API report update for declarative elements, lazy elements, DOM parts, and custom attributes #41
19. HTML modules - add HTML Modules entry to the report #60
20. Custom Attributes - docs: add API report update for declarative elements, lazy elements, DOM parts, and custom attributes #41

---

• 🚫 - has no delegate / owner, or needs help
• 🌟 - featured as part of our 2022 Report Outline #43

[thescientist13]

@Westbrook
Do you have any objections to keeping this issue pinned? I will also re-open too if that's OK (and I will unlink to PRs so GitHub doesn't keep auto closing).

[Westbrook]

I just took it off because it said “Closed”. If it’s not closed, let’s put it back. 🙈

[Westbrook]

@thescientist13 at what point might it be OK to close this and restart a new tracking issue?

[thescientist13]

Yeah, I think its a couple years past its time at this point, and not sure if this year is any insight into future precedence as this year we didn't prepare a report.

But the content can certainly be re-used / re-appropriated as need for future reports or other CG efforts!