Re: Default Values

Hi John, all,

Is the Explainer focused solely on Module 1? If so, then I think the only datatypes we have for the values of attributes are: token; token list and integer list (not sure if "integer list" is the correct W3C term, but something like that seems to fit @symbol—and perhaps we should qualify whether 0 is a valid symbol number).

(If I've missed something and we _do_ need to include something about true/false or true/false/undefined, I will need a bit more time to grok the invalid/default concepts.)

I just noticed that the list of attributes in §4.1 of the Explainer doesn't mention @simplification nor @distraction.

best regards,


Matthew
-- 
Matthew Tylee Atkinson
--
Senior Accessibility Engineer
TPG Interactive
https://www.tpgi.com

A Vispero Company
https://www.vispero.com

--
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.

On 20/04/2021, 19:04, "John Foliot" <john@foliot.ca> wrote:

    In the current draft of our Explainer document, Section 3.2 Values appears (to me) to have a redundant entry. It currently states: 
    The value may be one of the following types:
    true/false Value representing either true or false, with a default "false" value. true/false/undefined Value representing true or false, with a default "undefined" value indicating the state or property is not relevant.


    Question: do we really need to make this distinction? Taking a cue from the current HTML5 specification <https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#keywords-and-enumerated-attributes>, I believe we can remove the first entry, and likely echo some of the text from the HTML5 spec here as well:


    The value may be one of the following types:
    true/false/undefined
    Value representing true or false, with a default "undefined" value indicating the state or property is not relevant. If the attribute value matches none of the given keywords, but the attribute has an invalid value default, then the attribute represents that state. Otherwise, there is no default, and invalid values mean that there is no state represented.  
    When the attribute is not specified, if there is a missing value default state defined, then that is the state represented by the (missing) attribute. Otherwise, the absence of the attribute means that there is no state represented.


    While I've been comfortable up to this point making very minor grammatical changes, removing some content and augmenting this point feels "bigger" to me, and before I propose the change, I'd like to get some feedback from the group.

    Anyone?

    JF
    --

    John Foliot | Senior Industry Specialist, Digital Accessibility


    "I made this so long because I did not have time to make it shorter." - Pascal "links go places, buttons do things"

Received on Wednesday, 21 April 2021 20:30:25 UTC