[whatwg] Web Forms 2.0 - Comments on sections 1 and 2

[Dean Edwards]

whilst we're talking about numbers...
a common scenario in web apps is to have a separate format for 
displaying numbers (e.g. currencies). The user enters "19" but after 
tabbing to the next field this is then displayed as "$19.00". focus/blur 
events are usually used to format/unformat the underlying value. is it 
too late to formalise something like this by introducing a "format" 
attribute? i could have really used it on the last project i worked on.
-dean

David Hyatt wrote:
> Range does not imply two numbers IMO.  It simply implies that the 
> selection of a specific number is made within a specified range.  The 
> term "range control" or "ranged control" is a fairly standard one to 
> represent a slider with a single current value, and you can find it in 
> multiple deployed toolkits.
> 
> dave
> 
> On Jun 10, 2004, at 1:46 PM, Ian Hickson wrote:
> 
>> On Thu, 10 Jun 2004, David Hyatt wrote:
>>
>>>
>>> Please do not change the type from range.  This is a common term for
>>> slider controls, and you can find the same term used in all sorts of
>>> modern toolkits.
>>
>>
>> The point is the "type" attribute is giving the data type, not the widget
>> type. And the data type is not "range", which implies two numbers.
>>
>> -- 
>> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
>> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
>> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
> 
>