9904 2010-06-10 19:20:49 +0000 <progress> element: max IDL attribute should return 1 not 0 when the content attribute is missing 2010-10-04 13:57:59 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All CLOSED FIXED http://dev.w3.org/html5/spec/the-button-element.html#the-progress-element P3 normal --- 1 adrianba ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 36089 0 adrianba 2010-06-10 19:20:49 +0000 Propose to change "The max and value IDL attributes must reflect the respective content attributes of the same name. When the relevant content attributes are absent, the IDL attributes must return zero." to instead read something along the lines of: "The max and value IDL attributes must reflect the respective content attributes of the same name. When the value content attributes is absent, the value IDL attribute must return zero. When the max content attribute is absent, the max IDL attribute must return one." The reason is that in a previous paragraph, the spec says "Otherwise, if the element has no max attribute, or if it has one but parsing it resulted in an error, or if the parsed value was less than or equal to zero, then the maximum value of the progress bar is 1.0." It makes sense that if the progress bar is using 1.0 as its maximum value then this should be the value returned by the IDL attribute if the content attribute is missing. Without this, code that consumes the IDL attribute has to also include the logic above from the spec to know how the control will behave. 37479 1 ian 2010-08-16 21:15:32 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: This got fixed as part of responding to some related e-mailed feedback, I believe.