You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: