W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2009

[whatwg] progress/meter in spec

From: jackalmage <jackalmage@gmail.com>
Date: Thu, 24 Sep 2009 11:06:24 -0500
Message-ID: <dd0fbad0909240906g99165d3rd9ae99b46f75c605@mail.gmail.com>
On Wed, Sep 23, 2009 at 7:28 PM, Jim Jewett <jimjjewett at gmail.com> wrote:
> http://www.whatwg.org/specs/web-apps/current-work/ uses status.js and
> status.css to create a popup showing status.
> It shows status of the section (such as "Awaiting implementation
> feedback" or "Controversial Working Draft"), the number of tests, the
> number of demos, implementation status for each of (in practice) 5
> implementations, and last-updated information.
> Am I correct in believing that the implementation statuses would
> ideally be a set of <progress> elements, even though the progress
> level won't be likely finish (or even change) during one reading?
> (And the same for overall section status?)

I believe so, yes.  <progress> doesn't have to be js-animated to be useful.

> If so, it looks like this is an example of wanting to style based on
> an arbitrary number of categories/thresholds (here done with classes),
> and also a fairly good example of the sort of styling that might be
> desired. ?(Currently done with dt/dd for the implementation status.)

Very good elucidation of this use-case.  Interesting.

Now, though, should such information be exposed directly through the
element, or would it be better to have a css pseudoclass that handles
it?  :progress(min, max) matching a <progress> who's value is between
the two arguments?

Received on Thursday, 24 September 2009 09:06:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:52 UTC