-
Notifications
You must be signed in to change notification settings - Fork 154
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
Duration.prototype.{round,total}: Missing checks for too large date-time values #3015
Comments
@anba Are you sure it already has test coverage? I tried adding the assertion steps to the polyfill, and got no new test failures. Which ones fail on your end? |
Edit: Forgot to reenable the test262 tests which were failing because of this missing check. 😅 This is covered by
When the input is
creates a date-time valid outside the valid ISO date-time valids, because the time part is midnight. |
See #3015, which posits that these assertions are hit in existing test262 tests.
See #3015, which posits that these assertions are hit in existing test262 tests.
See #3015, which posits that these assertions are hit in existing test262 tests.
See #3015, which posits that these assertions are hit in existing test262 tests.
Temporal.Duration.prototype.round, steps 27.f-h:
Temporal.Duration.prototype.total, steps 12.f-h:
isoDateTime
andtargetDateTime
can be be outside the valid date-time limits, which breaks assertions inDifferencePlainDateTimeWithRounding
andDifferencePlainDateTimeWithTotal
when callingDifferenceISODateTime
.(This is already covered by test262 tests, but probably didn't get noticed because the polyfill doesn't implement the assertion steps.)
The text was updated successfully, but these errors were encountered: