Closed Bug 293811 Opened 20 years ago Closed 20 years ago

"dead zone" in thunderbird main window

Categories

(Thunderbird :: Mail Window Front End, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 270052

People

(Reporter: ranger, Assigned: mscott)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050429 Camino/0.8+
Build Identifier: version 1.0+ (20050509)

There is a dead zone in the thunderbird mail client that is unclickable.  This
has happened since I've used thunderbird, but it's gotten worse in recent builds.

It's reproducible every time, it also seems to grow in size up to a certain
point the longer I leave the app open.  (Actually, it seems to grow the more I
interact with the app.  If I use tbird a lot in a half hour time period, it can
happen that early, if I open it and leave it alone for 2 hours, it won't happen
yet.)

If I close the app and re-start it, the dead zone goes away.

In recent snapshot builds (post-1.0) it now also has a draw error where the dead
zone is (you can see it in the screenshot linked from the URL).

It includes everything below the button-bar (I can click "Get Mail", "Write",
etc., but not any folder in the folder listing that lines up with the dead zone.
 If I scroll so that different folders are showing in the folder listing, I can
click folders that I used to not be able to click, so it's definitely spatial
and not related to a certain set of folders inside the folder list.


Reproducible: Always

Steps to Reproduce:
1.  Start thunderbird
2.  Use thunderbird
3.  Try to click somethign in the upper-left area.  :)

Actual Results:  
unclickable
whups, I *thought* I'd opened a bug on this already, but couldn't find it
before.  Now I did.  ;)

Marking as duplicate of bug #270052.

*** This bug has been marked as a duplicate of 270052 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.