[Bug 13160] New: The progress element has redundant and confusing specification of value and max

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13160

           Summary: The progress element has redundant and confusing
                    specification of value and max
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: dominicc@chromium.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


This paragraph describing the progress element is confusing:

The value and max attributes, when present, must have values that are valid
floating point numbers. The value attribute, if present, must have a value
equal to or greater than zero, and less than or equal to the value of the max
attribute, if present, or 1.0, otherwise. The max attribute, if present, must
have a value greater than zero.

Presumably this refers to the attributes specified in the IDL, in which case
there is no possibility for them to be missing. So the "when present" language
is confusing.

If it refers to the attribute nodes, then it doesn’t specify what the UA should
do when an invalid value is parsed, set via setAttribute, etc.

Assuming that this refers to the attributes specified in the IDL, then I
believe that paragraph should be struck. The subsequent paragraphs specify what
value those attributes should have.

This came up at the bottom of this WebKit bug thread:
<https://bugs.webkit.org/show_bug.cgi?id=63861>

-- 
Configure bugmail: http://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 Wednesday, 6 July 2011 13:23:36 UTC