input type="time" stops toggling AM/PM when focussed
Reported by
zac.spit...@gmail.com,
Dec 3
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3628.0 Safari/537.36 Steps to reproduce the problem: 1. open https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/time 2. enter any hours and minutes 3. enter A for AM, AM/PM remains focussed 4. toggle between AM and PM using a and p keys What is the expected behavior? whilst focussed, pressing a or p keys should continue to toggle between AM and PM What went wrong? it stops toggling after the switching between AM to PM or vice versa Did this work before? N/A Chrome version: 73.0.3628.0 Channel: canary OS Version: 10.0 Flash Version: In Firefox it continues to toggle whilst focused. Edge has a different popup UI
,
Dec 4
zac.spitzer@ Thanks for the issue. Tested this issue on Windows 10 on the latest Canary 73.0.3630.0 and reported version 73.0.3628.0 by following the below steps. 1. Launched Chrome and navigated to https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/time. 2. On Windows, could observe that only the hours and minutes can be entered and no field is present to enter AM/PM. Attached is the screen shot for reference. Request you to check and provide a URL where this issue can be reproduced, which will help in further triaging. Thanks..
,
Dec 4
Might be the regional settings coming into play? my system is set to English Australia
,
Dec 4
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 5
zac.spitzer@ Thanks for the update. Able to reproduce this issue on Mac OS 10.13.6,Windows 10 by setting to System language to English India on the latest Stable 71.0.3578.80 and latest Canary 73.0.3630.0. Unable to test and confirm the issue on Ubuntu 17.10 as only the hours and minutes can be entered and no field is present to enter AM/PM. This is a Non-Regression issue as this behavior is observed from M-60 chrome builds. Hence marking this issue as Untriaged for further updates from Dev. Thanks.. |
||||
►
Sign in to add a comment |
||||
Comment 1 by phanindra.mandapaka@chromium.org
, Dec 3