[Bug 16067] New: Consistent use of 'no value' attributes. The 'no value' attributes like "selected", "checked" and "required" are being used inconsistently in the examples throughout the HTML5 specifications. Where "required" is always used with no value ('required' vs 'r

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16067

           Summary: Consistent use of 'no value' attributes. The 'no
                    value' attributes like "selected", "checked" and
                    "required" are being used inconsistently in the
                    examples throughout the HTML5 specifications. Where
                    "required" is always used with no value ('required' vs
                    'r
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification: http://www.w3.org/TR/html5/Overview.html
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
Consistent use of 'no value' attributes.

The 'no value' attributes like "selected", "checked" and "required" are being
used inconsistently in the examples throughout the HTML5 specifications.

Where "required" is always used with no value ('required' vs
'required="required"'), the "selected" as well as the "checked" attribute use
both the style with and without value ('selected="selected"' and 'selected').
There is also no mention about the possibility to use either of these styles,
let alone one style being recommended over the other.
Only one style should be used throughout the document, and one of the two
should preferably be recommended.

Personally I would even opt for a new attribute that takes one of the three
attributes above as values. This would get rid of these rather awkward
attributes all together. E.g.

'state="selected"', 'state="required"'

I, however, do not know how viable such a proposal will be if made by me if it
hasn't been by others already.

Posted from: 87.195.226.142
User agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:10.0.2) Gecko/20100101
Firefox/10.0.2

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 21 February 2012 22:32:19 UTC