RE: Ensuring "undefined" means undefined for aria-current

+1 to Joanie & Jason
JF
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: "White, Jason J" <jjwhite@ets.org> Date: 7/24/17  11:25 AM  (GMT-06:00) To: Joanmarie Diggs <jdiggs@igalia.com>, ARIA Working Group <public-aria@w3.org> Subject: RE: Ensuring "undefined" means undefined for aria-current 
+1 to Joanie's proposal. While I appreciate the difference between "undefined" as a literal value and the notion of an undefined value, this distinction needs to be better reflected in the spec to avoid the real potential for confusion.

> -----Original Message-----
> From: Joanmarie Diggs [mailto:jdiggs@igalia.com]
> Sent: Monday, July 24, 2017 12:20 PM
> To: ARIA Working Group <public-aria@w3.org>
> Subject: Ensuring "undefined" means undefined for aria-current
>
> Hey all.
>
> As I pointed out on the list [1], if aria-current is undefined because no value is
> specified, aria-current is false. But if aria-current is set to the value "undefined",
> aria-current is true. It was never (ever,
> ever) intended for undefined and "undefined" to be opposite values. And
> normally they aren't. We just have an oddball case with aria-current because the
> spec states the following for aria-current:
>
> "Any value not included in the list of allowed values should be treated by
> assistive technologies as if the value true had been provided."
>
> It is my proposal that we fix this oversight by making the following change:
>
> Existing text: "If the attribute is not present or its value is an empty string, the
> default value of false applies and the aria-current state MUST NOT be exposed
> by user agents or assistive technologies."
>
> Proposed text: "If the attribute is not present or its value is an empty string or
> <code>undefined</code>, the default value of false applies and the aria-current
> state MUST NOT be exposed by user agents or assistive technologies."
>
> I believe the above changes are editorial because surely no one thinks the string
> literal value "undefined" should mean the complete opposite of an undefined
> value. (Right? Right?? <smiles>)
>
> Feedback encouraged.
> --joanie
>
> [1]
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.w3.o
> rg%2FArchives%2FPublic%2Fpublic-
> aria%2F2017Jun%2F0058.html&data=02%7C01%7Cjjwhite%40ets.org%7C6e347
> c49b4804bb67c8f08d4d2affa19%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0
> %7C0%7C636365100638437670&sdata=xKyuiqhHYK5Q%2FUWFVH3JAJtl4B8kM
> Z2V7jAK8FQfXeE%3D&reserved=0


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________