Issue metadata
Sign in to add a comment
|
Number input has reversed digits
Reported by
bu...@jotform.com,
Dec 29 2017
|
||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. put an Number Input on a page wrapped in a label 2. apply width:0 CSS rule on the input field 3. log event.target.value on keyup/input event 4. type something from the SOFT KEYBOARD provided by device OS What is the expected behavior? logging the value in typed order What went wrong? it logs the value backwards. Can be reproducable via https://codepen.io/xzbd/full/dMgWzP/ Did this work before? N/A Chrome version: 4.3 Channel: stable OS Version: 6.0.1 Flash Version:
,
Dec 29 2017
It says 4.3 on Play Store. But it says 63 in change log. So it should be 63
,
Jan 2 2018
,
Jan 2 2018
burak@: Thanks for the report!! Could you please attach one more file where you're seeing this issue exactly as we are unable to enter the value's in the above mentioned file. If possible attach a screencast as well, that would help us in triaging the issue. Thanks!!
,
Jan 2 2018
Hey! You can find the screencast attached. Hope it'll be useful. Happy new year!
,
Jan 2 2018
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 5 2018
Burak@ Thanks for the update. Could you please attach a sample file along with the video as the above mentioned attachment doesn't have valid video file. Thanks!!
,
Jan 5 2018
I couldn't understand. Weren't you able to see the problem from the gif i uploaded? I've sent you the link of the setup(https://codepen.io/xzbd/full/dMgWzP/). What else do you need?
,
Jan 5 2018
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 11 2018
I couldn't reproduce this issue with a real Android device. Is <label> required? Is 'width:0' style required?
,
Jan 17 2018
Also, what environment did your reproduce this issue in?
,
Jan 17 2018
Hello, sorry for the late reply; i didn't notice the earlier email. And, yes both label and style required. Also, using the soft keyboard (not a physical keyboard but the keyboard provided from the device operating system) is the crucial part. I've experienced this problem with my personal device: Sony Xperia Z3 Compact and almost in every device provided in browserstack.com. Some friends of mine who are IOS users also experienced this misbehaviour. For debugging convenience i've created a new pen that you can observe the output on the page(also at the console): https://codepen.io/xzbd/full/YYJeRp/ P.S it works just fine on Desktop or simulating a device at browserstack.com while using the physical keyboard.
,
Jan 17 2018
Thank you for providing more feedback. Adding requester "tkent@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 18 2018
Hmm, this might depend on Android OS version and software keyboard type.
,
Jan 25 2018
The NextAction date has arrived: 2018-01-25
,
Mar 12 2018
Tested the issue in Android and able to reproduce the issue. Similar behavior is observed since Chrome #60.0.3072.0 Connect mouse to the device. Steps Followed: 1. Launched the Chrome Browser. 2. Navigate to https://codepen.io/xzbd/full/YYJeRp/ 3. Observed the values entering backwars Chrome versions tested: 60.0.3072.0, 65.0.3325.109(Stable), 67.0.3368.0(Canary) OS: Android 6.0.1 Android Devices: Samsung S& Keyboard(mouse integrated) used to test - Lenovo Thinkpad This seems to be a Non-Regression issue as same behavior is seen since M60. Untriaged for further input's on this issue. Please navigate to below link for log's and screen cast-- go/chrome-androidlogs/798095 Thanks! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by schenney@chromium.org
, Dec 29 2017