New issue
Advanced search Search tips

Issue 761552 link

Starred by 2 users
Status: Archived
Owner: ----
Closed: Sep 13
Cc:
pnangunoori@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Datetimelocal input components are

Reported by lax...@gmail.com, Sep 1 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063

Steps to reproduce the problem:
1. Create an HTML document with the following contents:
    <input type="datetime-local"></input>
2. Open an empty tab in Chrome.
3. Drag and drop the HTML document created in step 1 into Chrome.
4. Input a valid date into the datetime-local control that renders.
5. Tab/Shift-Tab through the control.

What is the expected behavior?
The right-hand buttons, (clear, spin buttons, calendar dropdown) should receive keyboard focus after the AM/PM segment.

What went wrong?
The right-hand buttons never receive keyboard focus.

Did this work before? No 

Chrome version: 52.0.2743.116  Channel: stable
OS Version: 10.0
Flash Version:

Comment 1 by pnangunoori@chromium.org, Sep 7 2017

Cc: pnangunoori@chromium.org
Labels: Needs-Milestonelabel OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Tested on latest Chrome Stable #61.0.3163.79, Chrome Beta #61.0.3163.79, Canary # 63.0.3207.0 and Chrome #50.0.2624.0 on Windows 7, Mac 10.12.6 and Ubuntu 14.04 and able to reproduce the issue.

This is a non-regression issue and able to reproduce from M-50 #50.0.2624.0. Marking it as untriaged so that issue gets addressed.

Attached the screencast and sample HTML file created for reference.

Thanks.
761552.webm
925 KB View Download
761552.html
54 bytes View Download

Comment 2 by robliao@chromium.org, Sep 13

Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Comment 3 by robliao@chromium.org, Sep 13 

Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Comment 4 by lax...@gmail.com, Oct 30 

Please reopen this issue. No UI elements should be keyboard-inaccessible to users. Chromium consumers need to meet accessibility compliance requirements.
►

Sign in to add a comment