Project

General

Profile

Feature #7245

NTP widget shows client time instead of server time

Added by Kill Bill over 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Web Interface
Target version:
2.3.4
Start date:
02/10/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

Description

The javascript nonsense dating back to Windows 9x/IE5 days actually shows local time on the client, severely confusing users.

Screen Shot 2017-07-21 at 09.30.34.png (9.47 KB) Screen Shot 2017-07-21 at 09.30.34.png Ben Montour, 07/21/2017 09:31 AM
Screen Shot 2017-07-21 at 09.30.26.png (17.7 KB) Screen Shot 2017-07-21 at 09.30.26.png Ben Montour, 07/21/2017 09:31 AM

History

#1 Updated by Jim Thompson about 4 years ago

  • Tracker changed from Bug to Feature
  • Target version set to Future

#3 Updated by Jim Thompson about 4 years ago

  • Assignee set to Jim Pingle

#4 Updated by Jim Pingle about 4 years ago

  • Status changed from New to Feedback

PR Merged

#5 Updated by Jim Pingle about 4 years ago

  • Target version changed from Future to 2.4.0

#6 Updated by Charlie m about 4 years ago

Fix confirmed on real HW.... Thanks!

#7 Updated by Jim Pingle about 4 years ago

  • Status changed from Feedback to Resolved

#8 Updated by Jim Pingle about 4 years ago

  • Target version changed from 2.4.0 to 2.3.4

#9 Updated by Ben Montour almost 4 years ago

This appears to still be pulling local time in 2.3.4-RELEASE-p1.
Was this fix part of 2.3.4 or am I misreading something?

#10 Updated by Jim Pingle almost 4 years ago

The fix was in 2.3.4 and any release after that.

It is not pulling local time. I just confirmed it by loading the same dashboard with NTP widget on two systems, one of which has a clock running 3 minutes slow. The NTP widget displayed the correct time on both clients.

#11 Updated by Ben Montour almost 4 years ago

Jim Pingle wrote:

The fix was in 2.3.4 and any release after that.

It is not pulling local time. I just confirmed it by loading the same dashboard with NTP widget on two systems, one of which has a clock running 3 minutes slow. The NTP widget displayed the correct time on both clients.

Maybe this is something different then. All times are set Etc/UTC as per default. Is there a different place I should report this?

#12 Updated by Jim Pingle almost 4 years ago

Start a new bug report for that. It may be using the local time zone incorrectly but it is not using the local clock which is what this ticket was about.

Also available in: Atom PDF