input[type=number] UI should reject invalid characters.

input[type=number] UI should reject invalid characters.

A number field silently ignores characters which can't be included in a
number.

It still accept invalid strings consisted of valid characters like "+++".

BUG=365196
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=194269

[tkent, 2015-04-23 05:49:33]

Patchset #1 (id:1) has been deleted

[tkent, 2015-04-23 05:50:59]

tkent@chromium.org changed reviewers:
+ keishi@chromium.org

[tkent, 2015-04-23 05:51:00]

Keishi, please review.

[keishi, 2015-04-23 06:36:03]

On 2015/04/23 05:51:00, tkent wrote:
> Keishi, please review.

LGTM.

I have a couple of concerns.
BeforeTextInsertedEvent is only called after composition is confirmed so I can
still use something like Google Japanese Input's calculator feature and enter
"1+1=".
If I paste "1．5" or "−15" with a zenkaku characters this will automatically
change it to 15 and the user might not notice.

[tkent, 2015-04-23 06:47:53]

On 2015/04/23 06:36:03, keishi wrote:
> I have a couple of concerns.
> BeforeTextInsertedEvent is only called after composition is confirmed so I can
> still use something like Google Japanese Input's calculator feature and enter
> "1+1=".

Right.  It sounds useful :)

> If I paste "1．5" or "−15" with a zenkaku characters this will automatically
> change it to 15 and the user might not notice.

Before this patch, they made input.value an empty string. Ignoring full-width
characters is not worse than the current.
Accepting full-width characters would be a separated issue.

[tkent, 2015-04-23 07:17:17]

The CQ bit was checked by tkent@chromium.org

[commit-bot: I haz the power, 2015-04-23 07:17:35]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1100273002/20001

[commit-bot: I haz the power, 2015-04-23 07:21:37]

Committed patchset #1 (id:20001) as
https://src.chromium.org/viewvc/blink?view=rev&revision=194269