Closed
Bug 1551893
Opened 6 years ago
Closed 6 years ago
Disallow non-zero-padded time element in Date.parse if time part marker T exists
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
RESOLVED
FIXED
mozilla68
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: saschanaz, Assigned: saschanaz)
Details
(Keywords: parity-chrome, parity-safari, site-compat)
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
Date.parse("2019-05-15T1:1:1")
Actual results:
1557849661000
Expected results:
NaN
Bug 1500748 conditionally requires zero pads for date element but it still always permits non-padded time element of ISO8601.
Assignee | ||
Updated•6 years ago
|
Component: Untriaged → JavaScript Engine
Product: Firefox → Core
Assignee | ||
Updated•6 years ago
|
Keywords: parity-chrome,
parity-edge
Assignee | ||
Updated•6 years ago
|
Keywords: parity-edge
Assignee | ||
Updated•6 years ago
|
Keywords: parity-safari
Assignee | ||
Comment 1•6 years ago
|
||
Make T as a strictness marker for ISO8601 time element, as it already does for the date element.
Comment 3•6 years ago
|
||
yes
Assignee: nobody → saschanaz
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Flags: needinfo?(arai.unmht)
Assignee | ||
Updated•6 years ago
|
Keywords: checkin-needed
Pushed by ncsoregi@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/00a761b7fce8
Require strict zero-pad for time element if T exists r=arai
Keywords: checkin-needed
Comment 5•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Comment 6•6 years ago
|
||
Posted site compatibility note: https://www.fxsitecompat.com/en-CA/docs/2019/date-parse-no-longer-accepts-illegal-iso-8601-date-time-formats/
Keywords: site-compat
You need to log in
before you can comment on or make changes to this bug.
Description
•