What about set the default start time for currentTimeMarker. Currently currentTimeMarker follows the browser time. This behaviour for each user login that has their own Time Localization. e.g. User A has Sydney time zone (UTC+10.00 Melbourne) then server will send the specific time to the Scheduler and currentTimeMarker will start based on that particular time. Event if User A look at scheduler in PC that use Kuala Lumpur time zone (UTC+08.00 Kuala Lumpur). Maybe add time Localization property for currentTimeMarker. But if it set null, it will follows current PC time.