Closed Bug 1739823 Opened 3 years ago Closed 2 years ago

In mini-month, when selecting a date in the future and clicking New Event, the Start Date is today's date instead of the future date selected

Categories

(Calendar :: Calendar Frontend, defect)

Product:
Calendar
Component:
Calendar Frontend
Version:
Thunderbird 95
Platform:
x86_64
Windows 10
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1791203

People

(Reporter: thee.chicago.wolf, Unassigned)

Details

STR / I feel like creating a new event used to work like so:

  1. select a future date on the mini-month calendar (i.e., January 31st, 2022)
  2. click on New Event
  3. the event start date would be the selected date in the future instead of defaulting to today's date

Expected:

  1. the start date of the new event was the future date selected

Actual:

  1. the start date of the event was today's date

It seems like I remember it always defaulting to the date selected.

Summary: In mini-month, when selecting a date in the future and clicking New Event, the Start Date is today's date instead of future date → In mini-month, when selecting a date in the future and clicking New Event, the Start Date is today's date instead of the future date selected
Product: Thunderbird → Calendar
Component: General → Calendar Frontend

I found the bug in TB 102.1.2 with a bit different behaviour (or I didn't understand this bug right). I made a bug report - Bug 1785783 "Calendar/Tasks suggests wrong date" (see: https://bugzilla.mozilla.org/show_bug.cgi?id=1785783). It's not a big thing, but a bit annoying if an used function gets suddenly lost.

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