Project

General

Profile

Actions

Feature #7245

closed
KB JP

NTP widget shows client time instead of server time

Feature #7245: NTP widget shows client time instead of server time

Added by Kill Bill over 9 years ago. Updated about 9 years ago.

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

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

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


Files

JT Updated by Jim Thompson over 9 years ago Actions #1

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

JT Updated by Jim Thompson over 9 years ago Actions #3

  • Assignee set to Jim Pingle

JP Updated by Jim Pingle over 9 years ago Actions #4

  • Status changed from New to Feedback

PR Merged

JP Updated by Jim Pingle over 9 years ago Actions #5

  • Target version changed from Future to 2.4.0

CM Updated by Charlie m over 9 years ago Actions #6

Fix confirmed on real HW.... Thanks!

JP Updated by Jim Pingle over 9 years ago Actions #7

  • Status changed from Feedback to Resolved

JP Updated by Jim Pingle over 9 years ago Actions #8

  • Target version changed from 2.4.0 to 2.3.4

BM Updated by Ben Montour about 9 years ago Actions #9

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?

JP Updated by Jim Pingle about 9 years ago Actions #10

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.

BM Updated by Ben Montour about 9 years ago Actions #11

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?

JP Updated by Jim Pingle about 9 years ago Actions #12

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.

Actions

Also available in: Atom