-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Date/parse/zero.js relies on implementation-specific behavior #4382
Comments
If all browsers currently comply already, though, then it's web reality, and we should probably update the spec to match. |
Browsers tend to copy the supported datetime string formats from each other as soon as a website relies on one so they likely all support it. I'm not building a web-facing engine though so I refuse to do that unless the spec tells me to :) |
It's probably best to file an issue at https://github.com/tc39/ecma262/ to clarify the "should" and "could" in https://tc39.es/ecma262/#sec-date.parse. Specifically:
and:
If these "should" are intended to be recommended but optional (similar to RFC 2119), then Note 1 in https://tc39.es/ecma262/#sec-date.prototype.tostring should probably slightly reworded so it doesn't sound like
|
Done: tc39/ecma262#3526 |
This test is for a non-normative note at the end of
Date.parse()
, which is only required to support the Date Time String Format. This works for parsing the output oftoISOString()
, but an engine is not required to make sense oftoString()
andtoUTCString()
datetime strings.Engines with extended support for non-standard datetime strings already have their own tests for those so IMO this test should be removed. At the very least it needs a feature flag.
https://github.com/tc39/test262/blob/main/test/built-ins/Date/parse/zero.js
The text was updated successfully, but these errors were encountered: