Feature #7245
closed
NTP widget shows client time instead of server time
0%
Description
The javascript nonsense dating back to Windows 9x/IE5 days actually shows local time on the client, severely confusing users.
Files
Updated by Jim Thompson over 7 years ago
- Tracker changed from Bug to Feature
- Target version set to Future
Updated by Kill Bill over 7 years ago
Updated by Jim Pingle over 7 years ago
- Target version changed from Future to 2.4.0
Updated by 
Updated by Jim Pingle over 7 years ago
- Target version changed from 2.4.0 to 2.3.4
Updated by Ben Montour over 7 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?
Updated by Jim Pingle over 7 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.
Updated by Ben Montour over 7 years ago
- File Screen Shot 2017-07-21 at 09.30.34.png Screen Shot 2017-07-21 at 09.30.34.png added
- File Screen Shot 2017-07-21 at 09.30.26.png Screen Shot 2017-07-21 at 09.30.26.png added
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?
Updated by Jim Pingle over 7 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.