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

Why is Date.now redefined so that it doesn't return milliseconds from 01-01-1970 as it's the default #172

Open
GoogleCodeExporter opened this issue Nov 30, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

1. call Date.now() without including date.js
2. call Date.now() including date.js

What is the expected output? What do you see instead?

expected: milliseconds from 01-01-1970
returns: a formated daqte like "Tue Apr 30 2013 15:39:18 GMT+0200 (CEST)"

What version of the product are you using? On what operating system?

1.0 Alpha-1 Chromium Ubuntu

Please provide any additional information below.

This raises a conflict with an other library wich expects Date.now to return 
milliseconds

Original issue reported on code.google.com by [email protected] on 30 Apr 2013 at 1:42

@GoogleCodeExporter
Copy link
Author

fixed in the current build in my fork: https://github.com/abritinthebay/datejs/

Original comment by [email protected] on 7 Sep 2013 at 12:26

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