Skip to content

Commit

Permalink
Normative: Disallow one day long time zone offsets
Browse files Browse the repository at this point in the history
Built-in time zones don't support an offset of `nsPerDay` nanoseconds and there
isn't any reason user-defined time zones should be able to support time zones
offsets of `nsPerDay` nanoseconds.
  • Loading branch information
anba authored and ptomato committed Sep 16, 2022
1 parent a3a8237 commit 9cc8b29
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion spec/timezone.html
Original file line number Diff line number Diff line change
Expand Up @@ -639,7 +639,7 @@ <h1>GetOffsetNanosecondsFor ( _timeZone_, _instant_ )</h1>
1. If Type(_offsetNanoseconds_) is not Number, throw a *TypeError* exception.
1. If IsIntegralNumber(_offsetNanoseconds_) is *false*, throw a *RangeError* exception.
1. Set _offsetNanoseconds_ to ℝ(_offsetNanoseconds_).
1. If abs(_offsetNanoseconds_) &gt; nsPerDay, throw a *RangeError* exception.
1. If abs(_offsetNanoseconds_) &ge; nsPerDay, throw a *RangeError* exception.
1. Return _offsetNanoseconds_.
</emu-alg>
</emu-clause>
Expand Down

0 comments on commit 9cc8b29

Please sign in to comment.