Ready for Trial: Element Reflection
Alice Boxhall
Contact emails
mere...@chromium.org, abox...@chromium.org, chri...@chromium.orgExplainer
https://github.com/WICG/aom/blob/gh-pages/explainer.md#reflecting-element-references
Specification
https://whatpr.org/html/3917/common-dom-interfaces.html#reflecting-content-attributes-in-idl-attributes:elementDesign docs
https://docs.google.com/document/d/e/2PACX-1vQnYgAdxwEBfa8tLhF9u-JmrZwZqeptPHZszpoBhbAQ008cFdV3aZfgmd3EuowvQ09DNazhkdPNY1jz/pub
Summary
This feature allows for ARIA relationship attributes to be reflected in IDL as element references rather than DOMStrings.
Blink component
Blink>DOMTAG review
https://github.com/w3ctag/design-reviews/issues/134TAG review status
CompleteRisks
Interoperability and Compatibility
Other browser vendors have been actively involved in shaping the API, and are present on the pull request thread, and supportive of the general idea. None have begun implementation. This initial implementation only affects a small set of ARIA attributes, so should be easily implementable in other browsers.
Gecko: No signal
WebKit: Neutral Representatives from WebKit have been actively participating in design discussions, but are waiting for developer feedback.
Web developers: No signals. Hoping to learn more from developers via a trial.
Ergonomics
This feature is being implemented on the AriaAttributes interface mixin, and rolled out as part of AOM Phase 1.
Activation
This feature is not completely polyfillable; ID references across shadow root boundaries are not possible to implement on top of existing APIs.
Goals for experimentation
Learn whether this helps developers use ARIA IDREF type attributes; particularly Custom Element authors using Shadow DOM.
Debuggability
In the short term, developers can use console.log to access the value for IDL attributes set via this API. Longer term, these attributes would be reflected in the Accessibility pane in the Elements panel.