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

[Bug 11937] Progress element should be indeterminate if the value attribute isn't a valid float

From: <bugzilla@jessica.w3.org>
Date: Fri, 25 Feb 2011 14:18:45 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PsyVJ-0005wq-Kr@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11937

Mounir Lamouri <mounir.lamouri@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |

--- Comment #3 from Mounir Lamouri <mounir.lamouri@gmail.com> 2011-02-25 14:18:45 UTC ---
> Rationale: The idea is you can trivially determine what kind of progress bar it
> is using a simple attribute selector rule, which makes doing things like
> mapping bindings easier.

Oh... My current implementation is using the :indeterminate pseudo-class. It
seems simpler. I should probably open a bug for that actually. 

> If there's a compelling reason to do otherwise, though, please feel free to
> reopen the bug (you don't actually give a reason in the comments above at all).

The reasons are multiple actually. First of all, it seems to make more sense to
make the progress indeterminate when you can't do anything with the value. That
would mean <progress value=""></progress> and <progress></progress> are
different: the first is determinate and the second isn't. In addition, that
way, progress.position != -1 would be a guarantee that progress @value is a
number which could save a few lines of JS, I guess.

-- 
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 Friday, 25 February 2011 14:18:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 25 February 2011 14:18:58 GMT