W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2010

[whatwg] <input type=number> without keyboard editing

From: TAMURA, Kent <tkent@chromium.org>
Date: Thu, 11 Nov 2010 12:31:42 +0900
Message-ID: <AANLkTin1Bdu4kRHbLFP94jaCJQD2inORz8sqKRpQPz+c@mail.gmail.com>
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
requirements
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
> decided
> 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  
> or
> another number type?

> --
> TAMURA Kent
> Software Engineer, Google












-- 
TAMURA Kent
Software Engineer, Google




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20101111/da043759/attachment.htm>
Received on Wednesday, 10 November 2010 19:31:42 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:28 UTC