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
With Custom Elements on the rise and the specification itself promoting the use of WAI-ARIA it is even more important to make this stuff as simple as possible.
The <taco-button> example illustrates how disabling a role="button" is supposed to work: by removing tabindex, onclick, onkeypress and adding aria-disabled="true" - that is a lot of DOM action necessary to compensate for something otherwise as simple as <button … disabled>.
It looks like form element semantics like [disabled] and :disabled will be available to Type Extensions (<input … is="my-cool-thing">) only.
The text was updated successfully, but these errors were encountered:
With Custom Elements on the rise and the specification itself promoting the use of WAI-ARIA it is even more important to make this stuff as simple as possible.
The
<taco-button>
example illustrates how disabling arole="button"
is supposed to work: by removingtabindex
,onclick
,onkeypress
and addingaria-disabled="true"
- that is a lot of DOM action necessary to compensate for something otherwise as simple as<button … disabled>
.It looks like form element semantics like
[disabled]
and:disabled
will be available to Type Extensions (<input … is="my-cool-thing">
) only.The text was updated successfully, but these errors were encountered: