Read the statement by Michael Teeuw here.
Default Clock wrong after update
-
@sdetweil and also, yes. prior to the upgrade, my general config was NOT set to a TZ prior to the upgrade. I
-
@drstang said in Default Clock wrong after update:
my general config was NOT set to a TZ prior to the upgrade.
correct… as there is no general timezone property
-
@sdetweil and what also confuses me is if I access the mirror via a web browser, the times are right!
-
@drstang I understand and agree with that…
the clock code runs in the browser… so one can only assume that the
moment code running in the browser is different between instances… -
@sdetweil Curious - are we still using Moment.js in default clock? I’ve heard issues relating with Moment and newer code - I think it might be failing to the point of no return.
-
@BKeyport AND it looks like we SHIP a copy… that is PROBABLY the problem
-
@sdetweil Makes sense - and certainly frustrating, as I realize I’m having issues with other modules that show times as well (showing sunrise/sunset, tide charts).
Any suggestions on a fix - as it is essentially making my MM unusable since my ‘main’ modules rely on time…
-
@drstang I am away til Tuesday.
not sure what a fix would be
-
@sdetweil I am a total novice at JS - but I fixed my modules by adjusting the configs - I incorporated moment-timezone.js and changed my code from ‘.local()’ to ‘.tz(America/New_York)’ Seems moment was having issues with the ‘local’ part of the code.
A bit annoying, and I’m sure another way could have been used, but the modules are at least showing correct time now!
-
@drstang Ahh, perhaps a forgotten requirement. It seems clear we need to get rid of Moment.js
