feat: add form-associated custom elements content #42
Conversation
| @@ -199,51 +203,157 @@ <h3>Links</h3> | |||
| <dt>Previous WCCG Report(s)</dt> | |||
| <dd><a href="https://w3c.github.io/webcomponents-cg/index.html#form-associated-custom-elements">2021</a></dd> | |||
| <dt>GitHub issues:</dt> | |||
| <dd>---</dd> | |||
| <dd><a href="https://github.com/whatwg/html/issues">https://github.com/whatwg/html/issues</a></dd> | |||
There was a problem hiding this comment.
Do we think we need / want a dedicated link to the issue instead of a repo? Just curious if that would be helpful from reader perspective? Or we also add this link in here at the top for reference?
https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements-face-example
There was a problem hiding this comment.
Yeah, I wrestled with that. Unfortunately there seem to be a number of separate issues since this really is a collection of features/APIs.
There was a problem hiding this comment.
I’d say a perponderance of links are better than a dearth. It could allow us to draw a fine line as to what does 2022 support look like down the line. However, I don’t see it specifically blocking this pass at the data!
| <dd>---</dd> | ||
| <dd> | ||
| <ul> | ||
| <li> |
There was a problem hiding this comment.
Is there a Mozilla stance link we could use? And should we link to chromestatus.com as well? Even when “shipped”.
| </section> | ||
| <section> | ||
| <h3>Status</h3> | ||
| <ul> | ||
| <li>---</li> | ||
| <li> |
There was a problem hiding this comment.
Is this the wrong place for that info?
| </ul> | ||
| </section> | ||
| <section> | ||
| <h3>Dissenting Opinion</h3> | ||
| <ul> |
There was a problem hiding this comment.
We might toss the whole section if there’s no dissension?
calebdwilliams
requested review from
thescientist13 and
Westbrook
and removed request for
thescientist13 and
Westbrook
Add initial content for form-associated custom elements