[whatwg] <input type=number> without keyboard editing
tkent at chromium.org
Wed Nov 10 19:31:42 PST 2010
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.
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
> such as 1 - 16. The number type control in Opera and WebKit allow a user
> 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
Software Engineer, Google
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg