Closed Bug 1773545 Opened 3 years ago Closed 3 years ago

After searching for and clicking on a past event on Calendar tab, any New Event start date will display date of the past event that was clicked on

Categories

(Calendar :: Calendar Frontend, defect)

Thunderbird 102
x86_64
Windows 10
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: thee.chicago.wolf, Unassigned)

Details

STR using 102.0b4:

  1. With TB 102.0b4 freshly launched and mini-month visible, click New Event and note the start date. Should be today's date.
  2. Open Calendar tab via Alt+3 or Events and Tasks > Calendar
  3. Using the search bar, search for some event / repeating event in the past you created (a few years ago works best) such a anniversary, birthday, etc. I used an event I created in April 2016.
  4. Once the event shows up in the search result, just click on it once to highlight it. Note that the date of the mini-Calendar at top-left has changed.
  5. Close the Calendar tab.
  6. Go back to mini-month and click New Event and note the start date (it will default to that date in the past from Step 4).
  7. Shake fist at screen angrily.

Actual Result:
The default start date is from the past event from Step 4

Expected Result:
Today's date

The only fix is to Alt+3 and click the "Go To Today" button else it will stay stuck on that date in the past forever when creating a new event.

OS: Windows 11 → Windows 10

Conversely, this will also occur if you do step 3 & 4 and search for an event in the future.

Component: General → Calendar Frontend
Product: Thunderbird → Calendar

Could this also be a duplicate of bug 1791203 which has been fixed in Thunderbird 106 beta?

So I went back to this issue to see how things stand with 106.0b1 and the STR doesn't repro the issue anymore. Looks to be fixed. Though the resulting action from steps 4 & 5 will leave the highlighted date selected, a shutdown and restart of TB will revert back to today's date. Closing as WFM.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.