[Bug 10988] add slider element

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10988

--- Comment #9 from Shelley Powers <shelleyp@burningbird.net> 2010-10-09 19:25:00 UTC ---
(In reply to comment #8)
> (In reply to comment #7)
> > For instance, if the range increments by 1, which is the default, but you want
> > indicators at values of 5, this is additional information that cannot be
> > captured in CSS, because it's related to data, not rendering. 
> 
> Actually you can already do that with the "list" attribute. See the example at:
> 
> http://dev.w3.org/html5/spec/number-state.html#range-state
> 
> > In fact, some JS libraries already allow, or are working on allowing, the
> > developers to apply labels to these tick mark indicators.
> 
> And you could do that with the "list" attribute pointing to suggestions with
> the "label" attribute:
> 
> http://dev.w3.org/html5/spec/number-state.html#range-state
> 
> http://dev.w3.org/html5/spec/common-input-element-attributes.html#the-list-attribute

That sounds like it could work, and matches what Jim needs. The suggested
rendering for range does seem to say that the datalist options are synced to
the movement of the slider thumbnail. 

However, the datalist options don't print out, as a rendered label. And there's
nothing in the rendering that suggests this should happen. When I tested with
latest Webkit and Opera, the slider showed, but not the tick marks, or the
labels. And Opera, I believe, does support both range and datalist. Webkit
looks partially there[1], and the intention does seem to be to add markers --
but labels? Hard to say.

There was also no indication of snapping to anything, must less a rendered text
mark. Of course, neither browser would render a vertical slider, either.

And how would the tick marks/labels map from an accessibility perspective?
Right now, all that's mapped is role, value, min, and max. 

Some of these things might be controllable by CSS, but not all. So, with the
fact that almost every last aspect of range is an optional rendering, I'm not
sure we can really say range does meet Jim's needs--not as it is currently
described in the HTML5 spec. 

Do you think CSS can take up the slack for all of this?

[1] https://bugs.webkit.org/show_bug.cgi?id=27247

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Saturday, 9 October 2010 19:25:03 UTC