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

very localiced 1970-error #13

Open
axelGschaider opened this issue Apr 24, 2013 · 0 comments
Open

very localiced 1970-error #13

axelGschaider opened this issue Apr 24, 2013 · 0 comments

Comments

@axelGschaider
Copy link

Hi

we are using cutetime in our webproduct and I have a quite strange error.
We are all mostly using Chromium on Ubuntu Machines for development and just on my computer there is a problem where the displayed time is always 1.Jan 1970 (so probably timestamp '0')

This happens with my local development server, our test server and even in production. But NOT when I use another browser.

So it's save to say that it's a local Chromium thing

I'm not using any proxies (anymore), I turned off all extensions, looked through all preferences (twice) and updated my system. 'date' in cl gives me a sensible output. I don't see a JavaScript error in Chromiums console

Short: I'm lost.

This is not a big issue (to me) since it doesn't happen to ANYBODY else and I don't expect you to take me by the hand. But have you ever experienced or heard about this? Any ideas?

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

No branches or pull requests

1 participant