1740209 - time indicator in the calendar is not accurate

Status: RESOLVED DUPLICATE of bug 1690620

(Calendar :: Calendar Frontend, defect)

Description

[andre+pirum]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0

Steps to reproduce:

Open the calendar tab, and select for instance day or week view.

Actual results:

When viewing the calendar, the red line that is supposed to follow the current time is not accurate, and often stuck minutes before the real time.
This is a major bug as this is causing missing appointments.

Expected results:

The red line should always indicate the right time,

Comment 1

[WaltS48 [:walts48]]

Can someone clarify for me whether this is supposed to update every minute or every 15 minutes as I see it work in 91.3.0, and I thought was fixed in bug 1665374?

Reporter, are you expecting an update every minute?

Comment 2

[andre+pirum]

Ah! This is exactly the bug I have, but with Thunderbird 91.3.0, so perhaps there is a condition making the bug occurring again.
The time indicator is stuck about one hour behind, and only refreshes itself when closing then re-opening the calendar tab.
So perhaps the bug is not really closed.

Comment 3

[andre+pirum]

Attachment: thunderbird-9.15-time-indicator-position.png

This is a screenshot of the time indicator position, this morning, at 9h15. Closing and re-opening the calendar tab did not fix the issue.

Comment 4

[Nigel Kendrick]

Attachment: thunderbird red line.png

Seeing this in 91.8.0 (Windows 10).

This is not an extreme example, I have seen worse lag.

Current time is 11.43, red line implies it's nearer half past.

Comment 5

[Nigel Kendrick]

I've just seen in bug 1690620 that TB config can be used to change the value of calendar.view.timeIndicatorInterval, which is set to 15 mins by default. I have set the value to 1 minute.

I would have expected the line to be a real time indicator, so I am surprised that the default granularity is 15 minutes; that seems counter-intuitive and bad UX.

Hopefully changing the aforementioned value is the 'fix'!?

Comment 6

[Sean Burke [:leftmostcat]]

It sounds like there are two issues here: the default update interval is unintuitive (users expect it to match the current minute, not the most recent quarter hour), and it's possible for the indicator to stop updating. Both should be addressed by the linked bug.