Closed Bug 645327 Opened 12 years ago Closed 12 years ago
Today build 20110326 is broken on message in tab
With today build Mozilla/5.0 (Windows NT 6.1; rv:2.0pre) Gecko/20110326 Thunderbird/3.3a4pre when a message is opened in a tab a great zone is grayed and unreadable! removing removing -moz-appearance: -moz-win-borderless-glass fixes the issue
It has nothing to do with removing -moz-appearance: -moz-win-borderless-glass. With yesterday nightly (20110325) 'Open message in tab' works. With today nightly (20110326) I see also your Bug. When I exchange the omni.jar with the one from yesterday (with Aero Glass enabled) it works again. The bug must come from a landing between the two nightlys.
No longer blocks: 645294
(In reply to comment #1) > With yesterday nightly (20110325) 'Open message in tab' works. With today > nightly (20110326) I see also your Bug. When I exchange the omni.jar with the > one from yesterday (with Aero Glass enabled) it works again. yes you are right! pushlog on mozilla-central between 20110325 than 20110326 http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2011-03-25&enddate=2011-03-26
Also busted in standalone message window.(status bar at top, with no message) Mozilla/5.0 (Windows NT 5.0; rv:2.0pre) Gecko/20110326 Thunderbird/3.3a4pre ID:20110326030018
It depends of the position of the messagepane splitter. If the splitter is fully on bottom, no text is visible. Is the splitter in the middle, about the half of text is visible. And if the splitter is on top most position, only a little part on bottom is unreadable.
(In reply to comment #2) > pushlog on mozilla-central between 20110325 than 20110326 > > http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2011-03-25&enddate=2011-03-26 my mistake: it's comm-central not mozilla-central http://hg.mozilla.org/comm-central/pushloghtml?startdate=2011-03-25&enddate=2011-03-26
If I have my times "right" it's not bug 627829 Testing with an hourly build Source Built from http://hg.mozilla.org/releases/mozilla-2.0/rev/c5e4090374e6 The problem does not appear. There was however a comm-central merge http://hg.mozilla.org/mozilla-central/rev/bf68a4a3ef6a bug 618662 might be a candidate
(In reply to comment #6) > There was however a comm-central merge > http://hg.mozilla.org/mozilla-central/rev/bf68a4a3ef6a > > bug 618662 might be a candidate It won't ever be a mozilla-central change for 3.3x now. Here's how to be sure: - Look in nightly directory for *.txt: http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2011-03-25-03-comm-2.0/thunderbird-3.3a4pre.en-US.win32.txt 20110325030016 http://hg.mozilla.org/releases/mozilla-2.0/rev/c5e4090374e6 http://hg.mozilla.org/comm-central/rev/09548f4fdce3 http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2011-03-26-03-comm-2.0/thunderbird-3.3a4pre.en-US.win32.txt 20110326030018 http://hg.mozilla.org/releases/mozilla-2.0/rev/c5e4090374e6 http://hg.mozilla.org/comm-central/rev/9c76e9244b20 So no change in mozilla-2.0 revs. Comm-central range is: http://hg.mozilla.org/comm-central/pushloghtml?fromchange=09548f4fdce3&tochange=9c76e9244b20 My suspicion is therefore bug 627829 - what it changed fits the bill for causing this. I'll back it out locally and check before backing it out on the server.
I can reproduce this on my Mac. And the standalone window is also broken. Its a build with comm-central and mozilla-2.0.
OS: Windows 7 → All
I backed out bug 627829 as I'd confirmed it caused the issue on my local machine: http://hg.mozilla.org/comm-central/rev/57eebd88c533
Status: NEW → RESOLVED
Closed: 12 years ago
Hardware: x86 → All
Resolution: --- → FIXED
Whiteboard: [fixed by backout of bug 627829]
Now that I actually remember where the tinderbox builds reside; http://ftp.mozilla.org/pub/mozilla.org/thunderbird/tinderbox-builds/comm-2.0-win32/ :) This bug is verified fixed by backout of bug 627829 verified using: Mozilla/5.0 (Windows NT 5.0; rv:2.0pre) Gecko/20110325 Thunderbird/3.3a4pre ID:20110326135538
Status: RESOLVED → VERIFIED
Hardware: All → x86
You need to log in before you can comment on or make changes to this bug.