Closed Bug 1611150 Opened 5 years ago Closed 2 years ago

Calendar tab sometimes dragged out of main window when single clicking.

Categories

(Calendar :: Calendar Frontend, enhancement)

enhancement

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: adam.feakin, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

I have Thunderbird running in a single window with a tab for my mail and a tab for my Calendars. I am using the "provider for google calendar" to show the calendars from my google account.
I clicked the Calendar tab to view my calendar.

Actual results:

Sometimes when clicking on the Calendar tab it will disappear and then re-open in a new Thunderbird window leaving me with 2 Thunderbird windows. One with just my mail, and another showing mail and calendar.
The kind of behavior you would get from dragging the Calendar tab out of the main window.

I suspect it is something to do with Lightning or the Google provider being slow sometimes and causing Thunderbird to think I did actually drag the tab. Although this happens without moving the mouse at all, maybe just a couple of pixels, and definitely not leaving the Thunderbird window.

Expected results:

When clicking the calendar tab it should just show the calendar tab and not create a new Thunderbird window.

Severity: normal → S3

Does this still reproduce?

Component: Toolbars and Tabs → Calendar Frontend
Flags: needinfo?(de.berberich)
Flags: needinfo?(adam.feakin)
Product: Thunderbird → Calendar
Version: 68 → unspecified

I haven't noticed this problem for a very long time, and I am not able to reproduce it in Thunderbird 116.0b.

The calendar tab doesn't switch to a new window now unless dragged out of the current window, or quite a few pixels down away from the tab bar. This is the behaviour I would expect.

Flags: needinfo?(adam.feakin)
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(de.berberich)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.