Closed
Bug 1499635
Opened 6 years ago
Closed 2 years ago
Support step attribute for time and datetime-local inputs (for second precision)
Categories
(GeckoView :: General, defect, P3)
GeckoView
General
Tracking
(firefox63 wontfix, firefox64 wontfix, firefox65 wontfix, firefox66 wontfix, firefox100 wontfix, firefox101 wontfix, firefox102 fixed)
RESOLVED
FIXED
102 Branch
People
(Reporter: robwu, Assigned: m_kato)
References
Details
Attachments
(1 file)
datetime-local and time inputs default to a precision of one minute. The step attribute can be used to change the precision to seconds (and even milliseconds...), but the UI does not offer a way to input seconds. In bug 1498787, this bug was fixed on Fennec (for seconds only, not for milliseconds). In GeckoView, the bug is still present, as it uses different code to show UI for date/time input: https://phabricator.services.mozilla.com/D8667#209324
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Product: Firefox for Android → GeckoView
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → m_kato
Comment 1•6 years ago
|
||
Marking fix-optional for 65 and 66 so that these already triaged issues don't show up repeatedly in weekly regression triage. Happy to take a patch in nightly.
Assignee | ||
Comment 2•2 years ago
|
||
We should add stepValue to DateTimePrompt to support step attribute such as
<input type="date" step="10">
etc in GeckoView.
Also, we don't have any tests for max/min attribute, so we should add it too.
Pushed by m_kato@ga2.so-net.ne.jp: https://hg.mozilla.org/integration/autoland/rev/eb766ad8a80e Add step attribute value to DateTimePrompt. r=geckoview-reviewers,agi,calu
Comment 4•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox102:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
Updated•2 years ago
|
Comment 5•2 years ago
|
||
This is a longstanding bug so no need to uplift this fix to Beta 101.
status-firefox100:
--- → wontfix
status-firefox101:
--- → wontfix
You need to log in
before you can comment on or make changes to this bug.
Description
•