1932135 - Calendar current day does not update automatically to today's date after midnight

Status: NEW

(Calendar :: Calendar Frontend, defect, P2)

Description

[Corey Bryant]

Attachment: mini-calendar

The current day in the mini-calendar highlights today, however, on the large calendar, yesterday is still highlighted as the current day. If I close the calendar and re-open it, nothing changes. If I click "Go To Today", today will then be highlighted as the current day on the large calendar. I'm using month view. This seems to be intermittent. I'm on Ubuntu 24.04 with Tb 133.0b4. Also seen by Antony della Porta on macOS 14.7.2.

Comment 1

[Corey Bryant]

Attachment: large-calendar

Comment 2

[Corey Bryant]

This is possibly a regression that started with calendar changes that landed in 133.0b1.

Comment 3

[Antony]

deffo intermittent - been stable for a few days, however, up to tricks again this morning as per the screenshot

My platform is macOS 14.7.2 (23H304), TB currently 133.0b5 build 2

Not sure that it is version related though, but certainly been happening since 131 - on and off

Comment 4

[Antony]

Attachment: Screenshot 2024-11-21 at 09.58.31.png

see my last comment

will add other shots from previous examples

Comment 5

[Antony]

Attachment: Cal-date issue 06-11-1.png

Comment 6

[Antony]

Attachment: Cal-date issue 06-11.png

Comment 7

[Antony]

Attachment: Cal-date issue 09-10-1.png

this shot is interesting as it shows two issues, which may be related.

I reported at this time that the week was starting on the wrong day from settings (and in the config)!

It also shows the wrong day high-lighted

I did test if it was a time zone thing, but was still like this later in the day-eve

Comment 8

[Antony]

update: not seen this issue for the last couple of TB and/or macOS beta updates

Comment 9

[Antony]

its back again, on 134.0b3, today is friday and cal ahs 5 thu highlighted

Comment 10

[Antony]

So I just changed an event and the cal jumped back a day for the highlighted Date/Day

This morning it was correct with Sunday 8th and date highlighted, now its Saturday 7th

Comment 11

[Toby Pilling [:tobyp]]

Hey there gents, Does this still happen? I think Geoff fixed this in bug 1757341

Comment 12

[Antony]

(In reply to Toby Pilling [:tobyp] from comment #11)

Hey there gents, Does this still happen? I think Geoff fixed this in bug 1757341

Seems good for last few betas

Comment 13

[Toby Pilling [:tobyp]]

Looks like this got fixed this in bug 1757341

Comment 14

[Corey Bryant]

I'm reopening this as it appears to still be occurring.

Antony reported today that in testing 136.0b1: Calendar up to its tricks again with the date/day lag in the main calendar, the side window is reflecting the correct date

Comment 15

[Antony]

and its up to its tricks once more

136.0b2

Today is yesterday on the main display, mini side cal, today is today!

Comment 16

[Geoff Lankow (:darktrojan)]

The mini calendar on that side of the screen is not connected to the main calendar, it only affects the panel it is in. Only the mini calendar on the left hand side is connected to the main calendar.

Comment 17

[Toby Pilling [:tobyp]]

Thanks Geoff, I assume that "today" should be consistent across the left, the main and the right calendars which is what I think Antony is reporting a problem with.

I was wondering if this might be related to the doMidnight fix in bug 1757341. In that fix, do all of those items get updated?

Antony, do you have steps to reproduce? Is it wrong intermittently?

Comment 18

[Antony]

(In reply to Toby Pilling [:tobyp] from comment #17)

Thanks Geoff, I assume that "today" should be consistent across the left, the main and the right calendars which is what I think Antony is reporting a problem with.

I was wondering if this might be related to the doMidnight fix in bug 1757341. In that fix, do all of those items get updated?

Antony, do you have steps to reproduce? Is it wrong intermittently?

Toby - do not have any way to be able to reporduce, as no idea of the possible cause, and yes, seems to be rather intermittent as working alright at the moment - though does that, then open TB next morning and it has NOT progressed,
It may be linked to TB be the focus on ly floptop the night before when I close the lid, so its the app i see when I open up the next day and the day seems to be lagging at that point,

Comment 19

[Antony]

TB was not the Focus app when I opened up the floptop this morning, from Standby, and date has lagged - only thing to note is that it is stuck on previous day, and this was the Focus yesterday - meaning I had selected the day and left it selected - maybe that could cause the date to not advance to next day - see attached recent screenshot

My image in comment 7 shows the same situation!!!

Comment 20

[Antony]

Attachment: Screenshot 2025-03-13 at 09.06.26.png

Comment 21

[Antony]

so i left cal with Sun selected so whole box highlighted - it is still selected and the cal als well, meaning the cal date selector has not moved to tues, so I suspect that if the focus is left ona particular day, cla does not change

Comment 22

[Antony]

Attachment: Screenshot 2025-04-09 at 21.17.11.png

Comment 23

[Geoff Lankow (:darktrojan)]

(In reply to Geoff Lankow (:darktrojan) from comment #16)

The mini calendar on that side of the screen is not connected to the main calendar, it only affects the panel it is in. Only the mini calendar on the left hand side is connected to the main calendar.

Apparently I wasn't clear enough. Include the sidebar on the left, the one with the list of calendars, if you're going to post a screen shot.

Comment 24

[Magnus Melin [:mkmelin]]

Antony, can you provide an updated screenshot?

Comment 25

[Rob Janssen]

(In reply to Antony from comment #21)

so i left cal with Sun selected so whole box highlighted - it is still selected and the cal als well, meaning the cal date selector has not moved to tues, so I suspect that if the focus is left ona particular day, cla does not change

I observe this as well, in the 128.9.0 ESR version. I had wednesday selected, the calendar tab not in view, and when I went to the calendar tab today (friday) the current day in the main calendar was still on wednesday. Clicking around the days did not change that, but closing/re-opening the program fixed it. Probably people who close down their computer at the end of the day do not notice this at all.

Comment 26

[Antony]

(In reply to Rob Janssen from comment #25)

(In reply to Antony from comment #21)

so i left cal with Sun selected so whole box highlighted - it is still selected and the cal als well, meaning the cal date selector has not moved to tues, so I suspect that if the focus is left ona particular day, cla does not change

I observe this as well, in the 128.9.0 ESR version. I had wednesday selected, the calendar tab not in view, and when I went to the calendar tab today (friday) the current day in the main calendar was still on wednesday. Clicking around the days did not change that, but closing/re-opening the program fixed it. Probably people who close down their computer at the end of the day do not notice this at all.

and still happening with 138.0b4 build2. i had Thu last week selected and the date highlight is stuck there, today being sunday
I dont shut my flotop down, just close the lid, so reckon you are right, Rob, on the shutdownor TB closing - date does not advance from highlighted day if one does not refresh

Comment 28

[Corey Bryant]

Antony, can we close this bug as fixed?

Comment 29

[fe_60]

Issue persists here with 140.1.1esr on Windows 10. Mini calendar has focus on today, while the main calendar still highlights yesterday. TB was running minimized to tray on my PC being in sleep mode over night. Closing the calendar tab and opening it again doesn't help. Only after a full restart of TB the correct date is highlighted in the main calendar.

Comment 30

[Toby Pilling [:tobyp]]

Hi all,
I've been watching this for the past week by waiting for midnight to roll around, testing various selections and situations in month view and week view - but have yet to see a situation where the mini calendar on the left doesn't match the main calendar.

If anybody can send screenshots of both calendars side by side and point out any selections made prior to the problem it would help a lot. Also knowing timezone, platform and version would be great.

Please don't include any unexpected situations involving the "Today Pane" calendar on the right - as Geoff mentioned previously, that is not "connected" to the main calendar in the same way as the mini calendar on the left.

The only time I managed to see a lag is if I had an event selected in the main calendar view.

Comment 34

[Antony]

(In reply to Toby Pilling [:tobyp] from comment #30)

Hi all,
I've been watching this for the past week by waiting for midnight to roll around, testing various selections and situations in month view and week view - but have yet to see a situation where the mini calendar on the left doesn't match the main calendar.

If anybody can send screenshots of both calendars side by side and point out any selections made prior to the problem it would help a lot. Also knowing timezone, platform and version would be great.

Please don't include any unexpected situations involving the "Today Pane" calendar on the right - as Geoff mentioned previously, that is not "connected" to the main calendar in the same way as the mini calendar on the left.

The only time I managed to see a lag is if I had an event selected in the main calendar view.

Well still happening, intermittently, now on 148.0b6 build 1

I did post screen shots above, yes with the Today as well mainly to show what the date/day should be reflected, the bug is always in the main Cal window, no matter the format.
I did (still do) suspect that it sticks when one has selected the previous day on that day and the next day that previous day is still selected and so is the hightlighted date/day

Comment 35

[Steve]

I have 2 units, 1 running 147.0.1, the other 147.0.2, both Win 11 Pro.
Neither are now showing the fault " Main Calendar not updating over midnight when unit opened from Sleep/Hibernate"

Comment 36

[bikubi]

I am also seeing this, on 148.0 on Arch. I had reported Bug 1792648 which got resolved with Bug 1757341, but it seems to have regressed.

Comment 37

[Geoff Lankow (:darktrojan)]

When it happens again, here's some debugging code you can try, paste these in the Error Console:

// Turn on calendar logging.
Services.prefs.setStringPref("calendar.loglevel", "All");
// Subscribe to notifications.
CalMetronome.on("minute", console.log);
CalMetronome.on("day", console.log);

That should print "minute" and the date on the console once every minute. If not, we're a bit closer to the problem. Try this:

CalMetronome.notify();

This should print minute and day notifications to the console and update today in the UI. If it does the first but not the second, that's weird but might tell us something useful. If it does the second without the first, that's very weird.

Why might the metronome stop ticking? The most likely reason I can think of is that it wasn't notified when the computer woke from suspend. If you suspend and wake up again, "[CalMetronome] Observed wake_notification" should be logged.

Comment 38

[bikubi]

(In reply to Geoff Lankow (:darktrojan) from comment #37)

When it happens again, here's some debugging code you can try, paste these in the Error Console:

Thanks, Geoff. Since my calendar is currently stuck on yesterday, I tried it right away...

// Turn on calendar logging.
Services.prefs.setStringPref("calendar.loglevel", "All");
// Subscribe to notifications.
CalMetronome.on("minute", console.log);
CalMetronome.on("day", console.log);

That should print "minute" and the date on the console once every minute.

It does.

If not, we're a bit closer to the problem. Try this:

CalMetronome.notify();

Ran this, did nothing (probably as expected).

This should print minute and day notifications to the console and update today in the UI. If it does the first but not the second, that's weird but might tell us something useful. If it does the second without the first, that's very weird.

Why might the metronome stop ticking? The most likely reason I can think of is that it wasn't notified when the computer woke from suspend. If you suspend and wake up again, "[CalMetronome] Observed wake_notification" should be logged.

FWIW, I suspended & woke up, and this did appear in the console log.

Comment 39

[Geoff Lankow (:darktrojan)]

Okay, well that's something. The function doMidnightUpdate is hooked up to the "day" notification. If it's not working properly I suggest opening that function in the developer tools debugger and stepping through it until something goes wrong.

I don't know what else could be wrong from here, recently I went through it all in depth to write a test that proves it all works, so at this point, 🤷‍♂️.

Comment 40

[Steve]

It seems to be working OK again in Ver. 149.0 - I'll check again tomorrow

Comment 41

[Steve]

It's worked OK again today. Can anyone else confirm for Ver. 149.0?

Comment 42

[Antony]

on TB 150.0b3 and still have the Cal day highlight issue - see screenshot

Comment 43

[Antony]

Attachment: Screenshot 2026-04-09 at 09.43.08.png

Comment 44

[Geoff Lankow (:darktrojan)]

Did you try the debugging steps in comment 37?

Comment 46

[Wayne Mery (:wsmwk)]

(In reply to Geoff Lankow (:darktrojan) from comment #44)

Did you try the debugging steps in comment 37?

Comment 47

[bikubi]

(In reply to Geoff Lankow (:darktrojan) from comment #39)

If it's not working properly I suggest opening that function in the developer tools debugger and stepping through it until something goes wrong.

I see the function and have set a breakpoint, but how do I trigger it? CalMetronome.notify(); doesn't do it.
(...as my calendar's today is currently stuck 7 days ago)
Thanks!

Comment 48

[Antony]

Attachment: Screenshot 2026-04-28 at 19.18.12.png

Still got the issue - see screenshot showing Mon highlighted but today is Tue

Comment 49

[Geoff Lankow (:darktrojan)]

I asked you try the debugging steps in comment 37 Antony. Please do that instead of posting yet more pictures that don't add any new information.

Comment 50

[Antony]

(In reply to Geoff Lankow (:darktrojan) from comment #49)

I asked you try the debugging steps in comment 37 Antony. Please do that instead of posting yet more pictures that don't add any new information.

Geoff, apols missed your comment. Having just run the 151.0b1 update the date sorts itself out, i'll keep an eye and run the code next time (maybe tomorrow :-) )

Comment 51

[Antony]

(In reply to Geoff Lankow (:darktrojan) from comment #49)

I asked you try the debugging steps in comment 37 Antony. Please do that instead of posting yet more pictures that don't add any new information.

tried both the code strings

reports the correct time, day, date for today, but the main cal window is still stuck on Wed
10:24:49.729 NotFoundError: No such JSProcessActor 'BrowserToolboxDevToolsProcess' 5
10:24:58.974 // Turn on calendar logging.
Services.prefs.setStringPref("calendar.loglevel", "All");
// Subscribe to notifications.
CalMetronome.on("minute", console.log);
CalMetronome.on("day", console.log);
10:24:58.999 undefined
10:25:00.895 minute
Date Fri May 01 2026 10:25:00 GMT+0100 (British Summer Time)
EventEmitter.sys.mjs:156:19
10:25:07.018
Object { }
background-RbH4RPhL.js:16358:17
10:25:32.716 CalMetronome.notify();
10:25:32.742 calendar: [CalMetronome] Scheduling one-off event in 27258ms CalMetronome.sys.mjs:108:14
10:25:32.744 undefined
10:26:00.035 minute
Date Fri May 01 2026 10:26:00 GMT+0100 (British Summer Time)
EventEmitter.sys.mjs:156:19
10:26:00.042 calendar: [CalMetronome] Starting repeating events CalMetronome.sys.mjs:113:14
10:26:08.663
Object { }
background-RbH4RPhL.js:16358:17
10:27:00.097 minute
Date Fri May 01 2026 10:27:00 GMT+0100 (British Summer Time)
EventEmitter.sys.mjs:156:19
10:27:08.640
Object { }

posted a screenshot as well

Comment 52

[Antony]

Attachment: Screenshot 2026-05-01 at 10.27.21.png

see above post

Comment 54

[Steve]

This fault seems to come and go with version releases - ver 149.0: OK, ver 150.0.0: fault back, Ver150.0.1: OK. What does that say?!?

Comment 55

[Wayne Mery (:wsmwk)]

(In reply to Steve from comment #54)

This fault seems to come and go with version releases - ver 149.0: OK, ver 150.0.0: fault back, Ver150.0.1: OK. What does that say?!?

Then I'd say it's related to something going on with your system, because AFAIK there have been no patches recently.

Comment 56

[Antony]

(In reply to Wayne Mery (:wsmwk) from comment #55)

(In reply to Steve from comment #54)

This fault seems to come and go with version releases - ver 149.0: OK, ver 150.0.0: fault back, Ver150.0.1: OK. What does that say?!?

Then I'd say it's related to something going on with your system, because AFAIK there have been no patches recently.

been happening for all updates, and is a prob right now as showing Fri, when today is Sat!

Comment 60

[Antony]

Attachment: Screenshot 2026-09-06 at 18.51.10.png

just for something different - main window date highlight is still lagging the real day, which is correct in the mini-month window

Comment 61

[Kalmer Piiskop]

I can reproduce this on Thunderbird 140.11.1esr (64-bit) on Ubuntu 24.04 / GNOME, Europe/Tallinn timezone.

System time and timezone are correct:

date:
Sun Jul 5 02:32:18 AM EEST 2026

timedatectl:
Local time: Sun 2026-07-05 02:32:19 EEST
Universal time: Sat 2026-07-04 23:32:19 UTC
RTC time: Sat 2026-07-04 23:32:19
Time zone: Europe/Tallinn (EEST, +0300)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

Thunderbird Calendar settings:
Use system timezone
Timezone shown as Europe/Tallinn
Date text format preview shows the correct current date.

Observed result:
After midnight, the main calendar view can still highlight the previous day as today. Clicking "Go to Today" refreshes it and the highlight moves to the correct day.

So this is not a system clock or timezone problem. It looks like the main calendar view fails to refresh the today marker after midnight.