Increased effort to edit existing calendar item
Categories
(Calendar :: Dialogs, defect)
Tracking
(Not tracked)
People
(Reporter: b3_web, Unassigned)
Details
Attachments
(1 file)
|
7.60 KB,
image/png
|
Details |
View item.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36
Steps to reproduce:
This bug is written against the calendar. As I did not find "calendar" or something similar in the "Component List", I had to write the bug against an existing component.
Steps to reproduce:
- Start Thunderbird
- Switch to the calendar view
- Create a new calendar item: enter title and description and a due date.
- Save the item. The item will appear in the calendar.
- Open the item with a double click in order to edit it
Actual results:
The item is not opened for editing. Instead, a new dialog is opened which shows me the properties of the item (see attachment "View item.png"). If I want to open the item for editing, I have to click the "Edit" button in addition.
Expected results:
For usability reasons, there should not be two user interactions needed in order to edit an item. In all previous versions, double clicking an item opened it for editing with just one double click. Now two are needed.
As editing an item is a very frequent operation, it should not be changed in a way that it is more complicated to open it from a usability perspective.
At least, there should be an option to bypass the new dialog if someone doesn't want to see it.
+1
Read in the release notes:
Calendar: Opening an existing event now opens summary dialog
This "summary view" is quite annoying/time-consuming when you only double-click calendar items in order to edit them (= default behavior since forever). So I would also like to suggest a preference to choose the default behavior, or a way to skip the "summary dialog".
Thanks! (love everything else in the TB 91.0 release)
+1
While I understand why some might prefer the new behavior, I find it quite annoying.
|
||
Comment 3•3 years ago
|
||
Your feedback is appreciated. In Bug 1685550, Alex (:aleca) has proposed a better UX. Currently tracked in bug 1685007.
Description
•