You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DSD templates for the b-* elements may or may not contain their built-in counterparts, but for the sake of this discussion, they might as well be totally custom, with contenteditable, or whatever.
I'd like to be able to 'fall back' to native behaviour for a FACE, so that it could participate in a form even with JS turned off. I have no strong opinions about how to accomplish this, it could be a bucket of attrs on the DSD template, or some global atts on the host, or some other solution.
The text was updated successfully, but these errors were encountered:
WCCG had their spring F2F in which this was discussed. You can read the full notes of the discussion (#978 (comment)) in which this was discussed, heading entitled "ARIA Mixin & Cross Root ARIA" as well as "ElementInternals/FACE lack of declarative / noscript" - where this issue was opened.
In the meeting, present members of WCCG reached a consensus to discuss further in breakout sessions. I'd like to call out that #1005 is the tracking issue for that breakout, in which this will likely be discussed.
Say I have a set of FACEs
Currently, I believe that supporting
<noscript>
essentially requires the page author to include someThe DSD templates for the
b-*
elements may or may not contain their built-in counterparts, but for the sake of this discussion, they might as well be totally custom, withcontenteditable
, or whatever.I'd like to be able to 'fall back' to native behaviour for a FACE, so that it could participate in a form even with JS turned off. I have no strong opinions about how to accomplish this, it could be a bucket of attrs on the DSD template, or some global atts on the host, or some other solution.
The text was updated successfully, but these errors were encountered: