[whatwg] <input type=number> without keyboard editing
diego.perini at gmail.com
Thu Nov 11 03:35:35 PST 2010
On Thu, Nov 11, 2010 at 4:31 AM, TAMURA, Kent <tkent at chromium.org> wrote:
> Thank you for many comments on this topic.
> I understand the team can use <select> or <input type=range>, and the team
> is actually using
> <input type=range> instead of <input type=number> for now.
> I'm not sure if the requirements of the team are common. But I'm afraid
> that type=number implementations for the current specification can't satisfy
> of actual Web application UI and type=number won't be used widely.
I am afraid to say the requirements of the team are not common.
<input type="number"> will be used when the requirements are common.
As said the team should use <select> if they care about backward compatibility.
Could you please explain why <select> doesn't meet the requirements or
why it is not preferred ?
> On Mon, Nov 1, 2010 at 11:31, TAMURA, Kent <tkent at chromium.org> wrote:
>> A team in Google tried to use <input type=number> for a product, and they
>> not to use it.
>> What they needed was a control to select an integer from a specific
>> integer range
>> such as 1 - 16. The number type control in Opera and WebKit allow a user
>> to input
>> out-of-range value even if the control has min=1 and max=16 attributes.
>> It's not
>> a good UI and the reason why they doesn't use type=number.
>> They need a number control which
>> - doesn't allow any keyboard / cut&paste operations and
>> So, a text field part is read-only, but the spin-buttons work.
>> - always has a valid value.
>> "required" by default, and sanitization algorithm may be different.
>> I'm not sure how to solve this issue. Introducing new content attribute
>> another number type?
>> TAMURA Kent
>> Software Engineer, Google
> TAMURA Kent
> Software Engineer, Google
More information about the whatwg