On Mon, 1 Nov 2010, TAMURA, Kent 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
On Wed, Nov 10, 2010 at 10:31 PM, TAMURA, Kent tk...@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
On Thu, Nov 11, 2010 at 4:31 AM, TAMURA, Kent tk...@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
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
On Nov 8, 2010, at 00:28, Boris Zbarsky wrote:
The original poster wanted the value to never be invalid period, not just at
submission time; this last is handled by form validation no matter what, no?
I'd expect number editing to work like an IME editing text: The user sees
intermediate
On Thu, Nov 4, 2010 at 8:55 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Hold. You (and the Google folks) were talking about always clamping stuff
as the user types, so the value is never invalid. So the user hits
backspace once, the value is 2, that's out of range, gets clamped to 20.
In my
On 01/11/2010 02:31, TAMURA, Kent 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
On 02/11/2010 11:46, Diego Perini wrote:
On Mon, Nov 1, 2010 at 3:31 AM, TAMURA, Kenttk...@chromium.org wrote:
A team in Google tried to useinput 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
On 11/7/10 2:05 PM, Aryeh Gregor wrote:
On Thu, Nov 4, 2010 at 8:55 PM, Boris Zbarskybzbar...@mit.edu wrote:
Hold. You (and the Google folks) were talking about always clamping stuff
as the user types, so the value is never invalid. So the user hits
backspace once, the value is 2, that's out
On Sun, Nov 7, 2010 at 5:28 PM, Boris Zbarsky bzbar...@mit.edu wrote:
OK, that's explicitly NOT what this thread was about to start with. The
original poster wanted the value to never be invalid period, not just at
submission time; this last is handled by form validation no matter what, no?
Interesting. I'm pretty sure I've seen pages that would break as a
result... I guess we'll see when a browser tries to do that.
from memory, microb did things like this, and it did break sites :).
such breakage is unfortunate, and the lack of flexibility/ability for
browser vendors to
On 11/7/10 5:47 PM, Aryeh Gregor wrote:
The problem with breaking scripts is that it might cause a UA to not be able
to ship the feature at all if it breaks existing content. That's why the
risk of breaking scripts is pretty important (my UA developer's hat on,
etc).
But is that a big deal
To: TAMURA, Kent tk...@chromium.org
Cc: whatwg wha...@whatwg.org
Sent: Sunday, November 07, 2010 4:48 PM
Subject: Re: [whatwg] input type=number without keyboard editing
On 01/11/2010 02:31, TAMURA, Kent wrote:
A team in Google tried to use input type=number for a product, and they
decided
Aryeh Gregor:
So if you wanted to change input type=number min=20 max=50 value=20
to 30, it would go like this:
It would be more interesting with “value=40”.
1) Hit backspace, user sees 2, .value is 20, no input event fired
2) Hit backspace, user sees , .value is , input event possibly
On Tue, Nov 2, 2010 at 9:58 PM, Boris Zbarsky bzbar...@mit.edu wrote:
This is difficult to do in practice. Consider:
input type=number min=20 max=50 value=20
The user now wishes to input 30 instead of the default value of 20. What
steps need to be taken to do this, and how does the input
On 11/4/10 7:57 PM, Aryeh Gregor wrote:
On Tue, Nov 2, 2010 at 9:58 PM, Boris Zbarskybzbar...@mit.edu wrote:
This is difficult to do in practice. Consider:
input type=number min=20 max=50 value=20
The user now wishes to input 30 instead of the default value of 20. What
steps need to be
On Fri, Nov 5, 2010 at 1:55 AM, Boris Zbarsky bzbar...@mit.edu wrote:
Presenting inconsistent state to script (see the value = value example
above) is not a good idea either, though.
Doing x.value = x.value while the user is typing is *always* annoying
to the user as it'll reset cursor and
On Tue, Nov 2, 2010 at 05:50, Aryeh Gregor
simetrical+...@gmail.comsimetrical%2b...@gmail.com
wrote:
On Sun, Oct 31, 2010 at 10:31 PM, TAMURA, Kent tk...@chromium.org wrote:
The number type control in Opera and WebKit allow a user to
input
out-of-range value even if the control has
On 11/01/2010 08:15 AM, Jonas Sicking wrote:
On Sun, Oct 31, 2010 at 7:31 PM, TAMURA, Kent tk...@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
On Mon, Nov 1, 2010 at 3:31 AM, TAMURA, Kent tk...@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
On Tue, Nov 2, 2010 at 4:46 AM, TAMURA, Kent tk...@chromium.org wrote:
Do you have any idea of improved UI with the perfect conformance?
I don't understand this question.
On Tue, Nov 2, 2010 at 7:14 AM, Mounir Lamouri mounir.lamo...@gmail.com wrote:
I'm not sure that disallowing out-of-range
On 11/2/10 3:57 PM, Aryeh Gregor wrote:
If the user enters a value of 100 ininput type=number max=50, then
it seems perverse to tell them The maximum allowed value is 50 so
they have to go back and fix it. It makes more sense to just
automatically clamp it to 50. Unless the user happens to be
On Mon, 2010-11-01 at 06:15 +0200, timeless wrote:
On Mon, Nov 1, 2010 at 4:31 AM, TAMURA, Kent tk...@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
On Sun, Oct 31, 2010 at 7:31 PM, TAMURA, Kent tk...@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
Ashley wrote:
set one in onchange
That's a javascript event, and shouldn't be relied upon for this sort of
thing really.
And my useragent is allowed to send arbitrary data to your server. you
*must* deal with it.
On Sun, Oct 31, 2010 at 10:31 PM, TAMURA, Kent tk...@chromium.org wrote:
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.
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
On Mon, Nov 1, 2010 at 4:31 AM, TAMURA, Kent tk...@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
28 matches
Mail list logo
