ISSUE-31: "undefined", instead of absent, value for "expanded" and similar states
undefined value
"undefined", instead of absent, value for "expanded" and similar states
- State:
- CLOSED
- Product:
- ARIA 1.0
- Raised by:
- Michael Cooper
- Opened on:
- 2007-09-10
- Description:
- Raised during June 2007 Face to Face http://www.w3.org/2007/06/27-pf-minutes.html
Some states and properties state that if the attribute is not provided, a particular behavior is assumed. However, the vagaries of DTD validation mean it's a little unpredictable as to whether an attribute will end up in the DOM, regardless of whether it was defined in the source code. Therefore, it is preferable to provide a value of "undefined" for such states and properties, and make it the default, as well as state that it is equivalent to the attribute not being present. This provides for the case in which the attribute ends up in the DOM unexpectedly, and also allows scripts to set the value to "undefined" if needed.
This wasn't an instant "yes" at the face to face meeting, so it was put on the agenda but never completed. - Related Actions Items:
- No related actions
- Related emails:
- No related emails
Related notes:
Discussed 17 September 2007 http://www.w3.org/2007/09/17-pf-minutes
implement proposal from http://lists.w3.org/Archives/Member/w3c-wai-pf/2007JulSep/0332.html except make “main†default for “channel†instead of add undefined
Display change log
