Open scottaohara opened 1 month ago
Name | Link |
---|---|
Latest commit | 32e060860fb15b29dee803667b198e095af35a67 |
Latest deploy log | https://app.netlify.com/sites/wai-aria/deploys/67069cb8cf16df0009437f36 |
Deploy Preview | https://deploy-preview-2341--wai-aria.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
talking with @aleventhal about this some more, we should also add in what to do about if someone uses the empty string, or puts in literal "garbage" text strings.
So this can probably be positive full numbers works as presently spec'd 0 and any negative number == indeterminate anything else == undefined and thus ignore.
So this can probably be positive full numbers works as presently spec'd 0 and any negative number == indeterminate anything else == undefined and thus ignore.
I know this is going to happen in a follow-up, but it's probably good if it's not too strict, e.g. spaces before and after the number are ok. I was going to do the following:
closes #1759 closes https://github.com/w3c/aria/issues/2346 also closes https://github.com/w3c/core-aam/issues/149
This PR adjusts the requirements for
aria-setsize
to fix the inconsistency between the ARIA and CORE AAM specs regarding the use of-1
as a value.Test, Documentation and Implementation tracking
Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.
Preview | Diff