1724075 - User flow is confusing when opening events in a tab

Status: NEW

(Calendar :: Dialogs, defect)

Description

[Philipp Kewisch [:Fallen][☁️📆]]

It seems we now have this flow where when editing an event, the summary dialog is shown first. I'm not quite sure why we added this and would love to get some more insight. When I double click on an event I'm expecting to make changes to it, I already have a summary of what is going on when viewing the event in the calendar views.

This aside, the flow is pretty awkward when you have the option enabled to show events in a tab. When you double click, the summary dialog opens as a dialog, then clicking edit takes you back to opening the event dialog in a tab.

Personally I feel we should revert the change that opens the summary dialog first, I'd like us to consider this for 91 so we are not stuck with the behavior for a whole ESR cycle.

Comment 1

[Alessandro Castellani [:aleca]]

Possibly related to bug 1724075.

Comment 2

[Richard Leger]

(In reply to Alessandro Castellani [:aleca] from comment #1)

Possibly related to bug 1724075.

I think Alessandro may have meant Bug 1685007 (and not this bug)
;-)

Comment 3

[Alessandro Castellani [:aleca]]

(In reply to Richard Leger from comment #2)

(In reply to Alessandro Castellani [:aleca] from comment #1)

Possibly related to bug 1724075.

I think Alessandro may have meant Bug 1685007 (and not this bug)
;-)

Ugh, my brain is still in vacation mode :D
Thanks Richard for the correct bug number.

Comment 4

[Magnus Melin [:mkmelin]]

(In reply to Philipp Kewisch [:Fallen] [:📆][:🧩] from comment #0)

It seems we now have this flow where when editing an event, the summary dialog is shown first. I'm not quite sure why we added this and would love to get some more insight. When I double click on an event I'm expecting to make changes to it, I already have a summary of what is going on when viewing the event in the calendar views.

That's basically the reason for the change: simply having the summary from the view is usually not enough at all. That goes for both physical events where I need to know the location and also the description. It goes double for online meetings, because then I need to get to the URL and other details.

Once an event is entered, I can think of very few cases where one would edit it, compared to actually seeing that information.

Comment 5

[Richard Leger]

(In reply to Magnus Melin [:mkmelin] from comment #4)

(In reply to Philipp Kewisch [:Fallen] [:📆][:🧩] from comment #0)

It seems we now have this flow where when editing an event, the summary dialog is shown first.
That's basically the reason for the change: simply having the summary from the view is usually not enough at all.

This issue is being discussed and addressed in a separate bugs, the last proposal from Akessandro (doorhanger) to resolve it is available in Bug 1685007 Comment 21.

Once an event is entered, I can think of very few cases where one would edit it, compared to actually seeing that information.

Magnus you may not think of them but it does not mean they don't exists out there. TB shall be flexible and let users decide how they want to use the application, not being imposed a workflow... that does not meet all needs... You seem to privilege reading over editing while both shall have equal footprint and easy access... some users may read more, accept some others may edit more... both should be possible in an easy way...let end-users decide...

Some discussion and arguments also already available in Bug 1685550.

Therefore this Bug 1724075 shall concentrate solely about Editing calendar items in Tab or not... personnally I am not convince that editing item in tabs may be useful but if it remain a user choice via preference I would be happy to try it out and see what I may prefer to decide from experience.
Again while the option would be welcomed, I don't think opening in tab shall be imposed.

Comment 6

[Lasana Murray]

I think we should get rid of the browser tabs all together. The extra space is nice but the way it opens up is distracting and takes you out of your area of focus. I think an improved design for calendar would be one you can do everything in the calendar tab. Almost like a single page application. Instead of dialog windows and browser tabs, we could show event information over the calendar view. We could also combine the summary and editing views into one allowing simple fields to be edited (by converting into inputs) on click and more complex ones via internal dialogs.

TB shall be flexible and let users decide how they want to use the application, not being imposed a workflow... that does not meet all needs... You seem to privilege reading over editing while both shall have equal footprint and easy access... some users may read more, accept some others may edit more... both should be possible in an easy way...let end-users decide...

While I agree TB should be flexible, that flexibility comes at a cost and is a burden carried by developers. I think having a clear design direction on how the product should be used results in both a better quality product and better developer experience. It's hard to improve things if you are unclear how it should work in the first place.