1681981 - Many chat contact notifications cause Thunderbird to be vertically larger than the screen

Status: RESOLVED DUPLICATE of bug 1673958

(Thunderbird :: Instant Messaging, defect)

Description

[Kai Engert [:KaiE:]]

After re-connecting my XMPP account after a while, around 90 spam contact requests had queued up.

(The chat was open, but the mail tab was selected.)

This caused automatic vertical resizing of the Thunderbird window. It had a height that was a multiple of the vertical screen size.

It was impossible to shrink the window size vertically.

Only after I discovered this cause, and after closing the notification, I was able to manually resize the window to a useful size.

Comment 1

[Magnus Melin [:mkmelin]]

I guess this was on 78? Probably bug 1673958 which is fixed on trunk.

Comment 2

[Kai Engert [:KaiE:]]

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

I guess this was on 78?

yes

Probably bug 1673958 which is fixed on trunk.

Alessandro, do you agree with Magnus that unfixed bug could be repsonsible for the symtom I've reported?

Comment 3

[Alessandro Castellani [:aleca]]

I think Magnus is correct.
As I wrote in the original comment of that bug:

"Also, since we're generating a new element at every call, we will never be able to properly stack notifications as we create a new container every time."

Which is what it seems to happen in your report.

We decided to not uplift it to 78 because we haven't had any report since 68 and changing the methods to tap notifications might break add-ons that use them.

I'll create a little script to visually test your scenario and confirm that it behaves properly on trunk.

Comment 4

[Alessandro Castellani [:aleca]]

I tested this with a couple of accounts and forcing multiple notifications (20 OTR verification requests).
The notifications properly stack on top of each other without increasing the window height.

Comment 5

[Kai Engert [:KaiE:]]

I think "worksforme" isn't the proper resolution.

I understand 78 is known to be broken, and later versions are known to be fixed, and it has been decided not to backport to 78.

I guess this should be a duplicate of the bug that fixed it on comm-central, bug 1673958

Comment 6

[Alessandro Castellani [:aleca]]

Indeed, this issue was fixed by bug 1673958