12119 2011-02-18 17:05:40 +0000 This section is not clear about how to make a progress element transition from determinate to indeterminate. As written, it sounds as if I'd have to call removeAttribute('value') to make it go into indeterminate mode. But I suspect that the intent is th 2011-08-04 05:04:56 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-progress-element P3 normal --- 1 contributor ian ian jackalmage mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 45805 0 contributor 2011-02-18 17:05:40 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html Section: http://www.whatwg.org/specs/web-apps/current-work/#the-progress-element Comment: This section is not clear about how to make a progress element transition from determinate to indeterminate. As written, it sounds as if I'd have to call removeAttribute('value') to make it go into indeterminate mode. But I suspect that the intent is that I can just set value to -1. But that isn't stated anywhere. --djf Posted from: 67.168.94.57 45807 1 jackalmage 2011-02-18 17:12:35 +0000 No, to make an indeterminate progress bar you must remove the @value attribute. Relevant spec quote: > Otherwise, if parsing the value attribute's > value resulted in an error, or a number less > than or equal to zero, then the current value > of the progress bar is zero. This clause is triggered by setting @value to -1 - it just makes the value 0. The -1 returned by the .position and .value properties just indicate that the progress bar is incapable of returning a valid number for either of these right now. 47982 2 ian 2011-05-04 22:15:03 +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: Accepted Change Description: see diff given below Rationale: I've tried to make this clearer by adding a note. 47983 3 contributor 2011-05-04 22:15:48 +0000 Checked in as WHATWG revision r6066. Check-in comment: clarify how to make a determinate and indeterminate progress bar http://html5.org/tools/web-apps-tracker?from=6065&to=6066 52867 4 mike 2011-08-04 05:04:56 +0000 mass-moved component to LC1