James Craig
James Craig
Ok then, let's work out the edge cases. 1. As Alice mentioned, some ARIA attrs are true booleans (`@aria-modal`), others are true/false/mixed, and still others are true/false/undefined, where the unset...
> The reflection doesn't change behavior because two attributes are related. And the types of the JS properties (IDL attributes) being strings versus numbers or any such doesn't change this....
Also, authors may be confused that they'd need to use boolean values to set some DOM properties, and boolean-like strings for others. ```js el.ariaModal = true; el.ariaInvalid = "true"; ```...
Note: I meant `ariaModal` above (corrected), but yes, the point is the same.
I don't think it's off topic. If the ARIA WG decides to reflect as something other than `DOMString`, it should reflect as many specific relevant types as possible, and potential...
> Oh, in that case, I think they would both use `= "true"`. Because `` does not work, right? It has to be ``? In that case, are you saying...
Thanks @domenic. @jnurthen @joanmarie Should we discuss these changes in the Thursday ARIA call?
@domenic and @annevk thanks for your help on this. @sinabahram reminded me yesterday that there are few numeric attributes where the absence of the attribute is meaningful. For example, a...
So potentially the following could default to `-1` * aria-posinset * aria-rowcount * aria-rowindex * aria-setsize `aria-value*` is a bit more complicated. ARIA has some other computed defaults in the...
Adding three reviewers that were prior contributors to #1018.