Re: Seeking clarification for "undefined" as a literal value

• From: Joanmarie Diggs <jdiggs@igalia.com>
• Date: Thu, 20 Jul 2017 01:12:43 +0200
• To: Aaron Leventhal <aleventhal@google.com>, Rich Schwerdtfeger <richschwer@gmail.com>
• Cc: ARIA Working Group <public-aria@w3.org>
• Message-ID: <9daab100-a137-22a5-47dc-948ebed44018@igalia.com>

On 07/19/2017 11:42 PM, Aaron Leventhal wrote:
> Rich, I see. But that means "undefined" = true for aria-current, which
> is counterintuitive for everyone. Right?

That's my take on it.

Given ARIA 1.1 is already in CR, I wonder if there is some editorial way
to declare the string literal "undefined" as a reserved value that
cannot be used where it is not explicitly supported. If we can do that,
then "undefined" (string literal) would be equivalent to undefined
(absent value) in the case of aria-current. Right?

--joanie

Received on Wednesday, 19 July 2017 23:13:23 UTC