Incubation / standardization process for new control primitives #6350
Description
As mentioned in #6349, once the early proposal for <popup> is a bit more mature and community-reviewed, we intend to take the idea to a community group for incubation before making more formal issues/PRs here.
We imagine new control elements such as <popup> would land in Open UI for incubation. Once incubated, we’ll make a more formal and mature proposal to WHATWG for the element definition, as well as any associated attributes and events. We’d like to invite anyone who wishes to help incubate the idea to participate in Open UI.
Open UI’s process is currently in progress of being documented, but long-term, the vision is that:
- Basic definitions of elements, attributes, and events would live in WHATWG
- CSS primitives will be defined in CSS specs
- Accessibility mappings will be hosted in the appropriate AAM spec (and any symmetric roles etc in ARIA)
- Open UI will continue to host a “mortar” spec that will describe how the control is expected to work, e.g. documentation of “light dismiss” behaviors that implementers should follow when implementing the
<popup>control; references out to the various other specs; etc. We imagine that the HTML living standard would cross-reference Open UI’s specification from the definition for implementer reference. - web-platform-tests would provide full coverage of all the above
The Open UI chairs (@gregwhitworth @una) and popup proponents would like to hear from the editors in WHATWG whether this long-term vision / ownership of concerns is workable. <popup> is only the first example of a control that would go through this process.