Remove implementation-specific code from ParseISOStyleDate
Categories
(Core :: JavaScript: Standard Library, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox121 | --- | fixed |
People
(Reporter: vinny.diehl, Assigned: vinny.diehl)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
As discussed here, it would be best to limit the scope of ParseISOStyleDate
to spec behavior:
https://tc39.es/ecma262/#sec-date-time-string-format
After D192671 lands, that function will continue to support formats which are not to-spec:
YYYY-MM-DD HH:mm:ss.sssZ
(space instead of'T'
)YYYY-MM-DD H:m:s.sssZ
(above, with single-digit hour|minute|second)
With the addition of TryParseDashedNumericDatePrefix
in bug 1557650, as well as support for 'Z'
timezone specifier in bug 1852422, we are getting close to being able to refactor this function to only support spec behavior.
I started working on this but ran up against bug 1863125, we'll need to look at that first. I'll upload a WIP patch for now.
Assignee | ||
Comment 1•1 year ago
|
||
The implementation-specific parsing for these types of dates is now
covered by TryParseDashedNumericDatePrefix, so we can do away with
this isStrict/isPermissive business now.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 3•1 year ago
|
||
bugherder |
Description
•