- From: <bugzilla@jessica.w3.org>
- Date: Mon, 07 Oct 2013 21:53:43 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13154 --- Comment #18 from Ian 'Hixie' Hickson <ian@hixie.ch> --- > Is value="2,5" a new micro-syntax? Insofar as a comma-separated list is a microsyntax, sure. > What about the possibilty of 'named' steps - so with the use of <option> > using a label instead of numeric value? What's the use case? > It would be better to retain the same conventions for Query/Form encoding > and avoid the syntax of value="" breaking out of HTML. The best reason for > this is so that APIs can remain the same when switching between different UI > controls, ie you should be able to swap an <input type="range"> for a > <select> with the same options and be able to interact with the same API. I don't follow. Can you elaborate? How does this impact <input type=email multiple>, for example? (It uses the same syntax as I'm suggesting here.) > The big difference is no <optgroup> for grouping - maybe this could be added > as valid content for <datalist>? The ability to demarkate groups within > scales is quite valuable, for example in temperature: Cold, Warm, Hot. This is getting pretty elaborate. At some point we have to draw a line and say "if you want a more elaborate control, use Web Components to make it yourself". I'm not sure which side of the line this suggestion should be on, though. Can you give concrete examples of what your suggestion would look like? > The multi-value email interface isn't really much of a UI control. It's exclusively a UI control, no? I don't follow. I don't really understand what a "list-building control" would be. Can you give an example of one? (I see two-point range controls all over the Web.) -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 7 October 2013 21:53:45 UTC