Bugzilla

(In reply to Alessandro Castellani [:aleca] from comment #71)
> I personally would like to restore the double click to edit after the doorhanger is implemented.
> So, 1 click to open the overview (doorhanger), and 2 clicks to edit.

Worthwhile proposal, should try this!

Please remember that Ctrl+single-click can *also* be used to select multiple events (not sure why Shift isn't implemented, maybe ux-error-prevention). So we also need to examine how the single-click doorhanger interacts with Ctrl+single-click selection. Maybe it's just fine, or we could suppress the doorhanger when Ctrl modifier is used to select events.

> Since the doorhanger in most cases will not open above the clicked event...

I hope the doorhanger will have some inbuilt flexibility to open to the appropriate side of the event where there's sufficient space to show it, and we should carefully test all edge cases (event at far-right, far-left, very top, very bottom, center-screen, small window etc.). Ideally, it should never cover the clicked event.

(In reply to Alessandro Castellani [:aleca] from comment #71)
> I personally would like to restore the double click to edit after the doorhanger is implemented.
> So, 1 click to open the overview (doorhanger), and 2 clicks to edit.

Worthwhile proposal, should try this!

Please remember that Ctrl+single-click can *also* be used to select multiple events (not sure why Shift isn't implemented, maybe ux-error-prevention). So we also need to examine how the single-click doorhanger interacts with Ctrl+single-click selection. Maybe it's just fine, or we could suppress the doorhanger when Ctrl modifier is used to select events.

> Since the doorhanger in most cases will not open above the clicked event...

I hope the doorhanger will have some inbuilt flexibility to open to the appropriate side of the event where there's sufficient space to show it, and we should carefully test all edge cases (event at far-right, far-left, very top, very bottom, center-screen, small window, today pane etc.). Ideally, it should never cover the clicked event.