W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 06 Jul 2011 17:42:50 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QeW7e-0000Nu-N7@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13160

Lucas Sa <lucas.sa@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lucas.sa@gmail.com

--- Comment #4 from Lucas Sa <lucas.sa@gmail.com> 2011-07-06 17:42:50 UTC ---
A bit later in the specification, you can see what UAs should do when there is
no value or max attributes:

"User agent requirements: If the value attribute is omitted, then the progress
bar is an indeterminate progress bar. Otherwise, it is a determinate progress
bar.

If the progress bar is a determinate progress bar and the element has a max
attribute, the user agent must parse the max attribute's value according to the
rules for parsing floating point number values. If this does not result in an
error, and if the parsed value is greater than zero, then the maximum value of
the progress bar is that value. 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."

Therefore, I understand that there is no problem with the "when present"
language.

-- 
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 17:42:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:13 UTC