Skip to content
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 broken in Safari 8 #274

Open
ljharb opened this issue Oct 18, 2014 · 0 comments
Open

Date.parse broken in Safari 8 #274

ljharb opened this issue Oct 18, 2014 · 0 comments

Comments

@ljharb
Copy link
Member

ljharb commented Oct 18, 2014

should be an invalid date
  Expected 1356998400000 to be falsy.
  Expected 1356948540000 to be falsy.
  Expected 1356955260000 to be falsy.
should work
  Expected 1333515722170.999 to be 1333515722170.
should support extended years
  Expected 8640000000000001 to be falsy.
  Expected -8640000000000001 to be falsy.
works with timezone offsets
  Expected 1327752000000 to be falsy.
  Expected 1327751940000 to be falsy.
  Expected 1327748460000 to be falsy.
  Expected -8640000000060000 to be falsy.
  Expected 0 to be 28800000.

One of these is because Safari 8 returns a non-integer value from Date.parse - I'm not certain if that's a feature (for profiling, so the tests should smooth it over) or if that's a bug (since the spec requires integers, and the shim should override).

Not sure about the others yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant