Closed Bug 1775105 Opened 3 years ago Closed 2 years ago

Clicking New Event in the event sidebar defaults to current date instead of chosen date in picker

Categories

(Calendar :: Dialogs, defect)

Thunderbird 102
x86_64
All
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1791203

People

(Reporter: bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

Steps to reproduce:

In the Today Pane, I have the mini calendar and the upcoming event list visible. Below the calendar there's a button to add a new event to the calendar.

Actual results:

When you click the New Event button, it opens up a prompt for adding a new event, but the selected event date is the current date instead of the day that is currently selected in the calendar above the button.

Expected results:

When you use the equivalent add event button inside the calendar tab, the selected date in the calendar is filled in as the suggested date for the new event. I think the same should happen when you add an event directly from the event sidebar.

Blocks: tb102found
Component: Untriaged → General
Product: Thunderbird → Calendar

I noticed that when a date is selected in the calendar tab in the background, that date is filled in instead of the current date.

Selecting a date in the Mini Month of the Today Pane, then selecting New Event, does use the selected date when I tested using 91.10.0 on Fedora Linux.

I can confirm the reporter's issue using version 102.0b8. Today's date will appear in the new event dialog.

Status: UNCONFIRMED → NEW
Component: General → Dialogs
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → x86_64
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE

Same as bug 1739823?

(In reply to Arthur K. [He/Him] from comment #4)

Same as bug 1739823?

I think so. Also resolved as duplicate of bug 1791203.

(In reply to Martin Schröder [:mschroeder] from comment #5)

(In reply to Arthur K. [He/Him] from comment #4)

Same as bug 1739823?

I think so. Also resolved as duplicate of bug 1791203.

Also, be aware of bug 1766835.

You need to log in before you can comment on or make changes to this bug.