Issue metadata
Sign in to add a comment
|
Cancelling keydown events for periods does not work in number inputs
Reported by
es...@henriksen.is,
Jul 30
|
||||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Set up a keydown event listener on a number input field 2. The keydown input field calls event.preventDefault() on events with key "." 3. Focus the input field 4. Type "." 3. See also the example file. What is the expected behavior? The event is cancelled and no period is input What went wrong? The event is not cancelled and the input recieves the key event, resulting in the comma being input. The key event has a type property of Unidentified and keyCode 229 (period ordinarily has a keyCode of 188). Did this work before? N/A Does this work in other browsers? Yes Chrome version: 67.0.3396.87 Channel: stable OS Version: 8.1.0 Flash Version: This is also the case with commas if lang is set to a language which accepts comma as a decimal separator. For example "nb". This works on chrome desktop.
,
Jul 31
Tested this issue on Android and able to reproduce this issue. Steps Followed: 1. Launched chrome 2. Naviagted to given html page, inputed some numbers and now inputed "." -- observed "." in number input field. Chrome versions tested: 60.0.3072.0, 68.0.3440.70 ; 70.0.3506.0(canary) OS: Android 9.0 Android Devices: Pixel XL This seems to be a Non-Regression issue as same behavior is seen from M-60 builds. Leaving the issue as Untriaged for further input's on this issue. Please navigate to below link for log's -- go/chrome-androidlogs/868894 Thanks!
,
Aug 1
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by chelamcherla@chromium.org
, Jul 31