Bug P3
Status Update
Comments
tk...@chromium.org <tk...@chromium.org> #2
[Empty comment from Monorail migration]
[Monorail components: -Blink>Forms]
[Monorail components: -Blink>Forms]
tk...@chromium.org <tk...@chromium.org> #3
[Empty comment from Monorail migration]
sh...@chromium.org <sh...@chromium.org> #4
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.
For more details visit
tk...@chromium.org <tk...@chromium.org> #5
[Empty comment from Monorail migration]
tk...@chromium.org <tk...@chromium.org> #7
[Empty comment from Monorail migration]
sh...@chromium.org <sh...@chromium.org> #8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
[Deleted User] <[Deleted User]> #9
[Empty comment from Monorail migration]
[Deleted User] <[Deleted User]> #10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
yu...@chromium.org <yu...@chromium.org> #11
[Empty comment from Monorail migration]
[Deleted User] <[Deleted User]> #12
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
at...@google.com <at...@google.com> #13
[Empty comment from Monorail migration]
mi...@gmail.com <mi...@gmail.com> #14
The issue still exists in the latest Google Chrome on Android
is...@google.com <is...@google.com> #15
This issue was migrated from crbug.com/chromium/461718?no_tracker_redirect=1
[Monorail mergedwith:crbug.com/chromium/895459 ]
[Monorail components added to Component Tags custom field.]
[Monorail mergedwith:
[Monorail components added to Component Tags custom field.]
Description
Version: 43 canary
OS: Android 5.0
What steps will reproduce the problem?
data:text/html,<input type=datetime-local step=1>
What is the expected output? What do you see instead?
Expected: Able to set seconds
Actual: There is no seconds field.
Please use labels and text to provide additional information.
<input type=time step=1> works as expected.