Closed
Bug 390288
Opened 17 years ago
Closed 15 years ago
Today Pane: Status bar disappears when enabling Today pane and Message pane in Wide View
Categories
(Calendar :: Lightning Only, defect)
Calendar
Lightning Only
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mschroeder, Unassigned)
References
Details
The Thunderbird status bar disappears when enabling Today pane and Message pane in Wide View.
Tb 2.0.0.6pre (20070730) + Lightning 0.7pre (2007073003) on WinXP
Flags: blocking-calendar0.7?
Comment 1•17 years ago
|
||
I don't see this issue on Windows 2000 regardless of the View layout.
Maybe you just make the Thunderbird window too small? The elements of the today pane have a minimum height set. If the Thunderbird window height is too small the Today pane will no longer fit and parts are off screen.
Reporter | ||
Comment 2•17 years ago
|
||
My Tb window is maximized and the screen resolution is 1024x768. After more testing, I also think the minimum height of the today pane is the reason for this behavior (maybe there is some minimum height also for the message pane). If the top of the message pane is higher than the bottom of the today pane with minimum height, the status bar disappears.
Updated•17 years ago
|
Flags: blocking-calendar0.7? → blocking-calendar0.7+
Comment 3•17 years ago
|
||
I removed the minimum height of the agenda-pane and todo-pane, and indeed this improved the behavior but solved the problem only partially. As Stefan mentioned already there is also a minheight set at the messenger window. I removed the min-heights already within my patch of https://bugzilla.mozilla.org/show_bug.cgi?id=388414 and therefor I suggest to set this issue to 'wontfix'.
Reporter | ||
Comment 4•17 years ago
|
||
(In reply to comment #3)
> I removed the min-heights already within my patch of
> https://bugzilla.mozilla.org/show_bug.cgi?id=388414 and therefor I suggest to
> set this issue to 'wontfix'.
WONTFIX is the wrong solution because it is a visible issue (and still a bug). We can set it to FIXED after your patch from bug 388414 has landed and this issue is fixed.
Comment 5•17 years ago
|
||
(in reply to comment #4)
As I said bug 388414 will not completely solve the problem, because there is still a min-height set at the messenger window of thunderbird which is beyond our implementation scope.
Comment 6•17 years ago
|
||
(In reply to comment #5)
This is understandable and acceptable. Restoring the default behavior is fine.
Thunderbird without Lightning: Issue starts at approx. 230 px window height
Thunderbird with Lightning: Issue starts at approx. 560 px window height
Comment 7•17 years ago
|
||
So after all, this seems to be out of our scope => WONTFIX after landing fix for bug 388414?
Comment 8•17 years ago
|
||
From my understanding this will be fixed (the default Thunderbird behavior is restored) by Bug 388414.
Comment 9•17 years ago
|
||
yes that's right. We can verify this after bug 388414 has been fixed.
Comment 10•17 years ago
|
||
- Berend will take care of that
- not blocking
Assignee: nobody → Berend.Cornelius
Flags: blocking-calendar0.7+
Comment 11•17 years ago
|
||
With the latest patch of bug 388414 I could see that the statusbar vanishes at a much smaller size, regardless if the todaypane was collapsed or not.
Updated•17 years ago
|
Target Milestone: 0.7 → ---
Comment 12•17 years ago
|
||
Martin, can this bug be closed?
Reporter | ||
Comment 14•16 years ago
|
||
(In reply to comment #12)
> Martin, can this bug be closed?
I think we should keep this bug open, and check again after moving to Trunk and while working on the Thunderbird integration. I still see a minor overlap of status bar and header area of the message pane in 0.9pre using Windows XP (Classic Theme).
Severity: normal → minor
Updated•16 years ago
|
Assignee: berend.cornelius09 → nobody
Reporter | ||
Comment 16•16 years ago
|
||
Has anyone observed the described behavior using Lightning 1.0pre?
Comment 17•15 years ago
|
||
I'll take that as a "no". Please reopen if the issue returns.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•