Closed
Bug 93101
Opened 23 years ago
Closed 23 years ago
Thread pane in mail & news wrong size when window initially opened with empty inbox
Categories
(Core :: XUL, defect)
Tracking
()
Future
People
(Reporter: peppe, Unassigned)
Details
Attachments
(1 file)
(deleted),
image/gif
|
Details |
The thread pane in mail & news is too narrow (by exactly the amount of the non-
existent scrollbar) when the mail & news main window is initially opened with
an empty inbox. It appears that the thread pane assumes that a scrollbar exists
and sizes itself accordingly. When one resizes the window or the splitter, the
thread pane becomes the right size.
I filed this on "xp toolkit/widgets: trees" because I assume the bug is in
outliner. (?)
Reporter | ||
Comment 2•23 years ago
|
||
Nope.. that's not the bug. What I'm talking about manifests itself so that I
can see the focus border around the outliner being too narrow on the right
side. It looks like it assumes there is a scroll bar when there really is none.
I can reproduce it every time with the latest nightly build (August 1st, early
morning build) by opening up the mail & news window with an empty inbox. The
focus is on the thread pane, but the focus border is too far from the right
edge. Resize the window and the focus snaps all the way to the right edge of
the window like it should.
Comment 3•23 years ago
|
||
-> Future.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → Future
Reporter | ||
Updated•23 years ago
|
Blocks: advocacybugs
Reporter | ||
Comment 5•23 years ago
|
||
Invalid? How is this *invalid*? What do you want? A screenshot? It's a very
obvious bug.. Can you point me to a duplicate or show me that it doesn't occur
or what? How can you just mark it as invalid without at least asking for more
info first?
Comment 6•23 years ago
|
||
Okay, it's the world's most trivial, pointless bug.
No longer blocks: advocacybugs
Severity: normal → trivial
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Reporter | ||
Comment 7•23 years ago
|
||
That's not what 92997 means. 92997 is for tracking bugs that
immediately "strike the viewer in the face". "Obvious" bugs.. It's not "easy
bugs"..
Comment 8•23 years ago
|
||
A new mail outliner lands soon (see bug 73865). It's highly probable that this
bug will be squashed by that landing. However that does not make it invalid.
Reporter | ||
Comment 9•23 years ago
|
||
Comment 10•23 years ago
|
||
See a screenshot of the mail window with the new outliner (illustrating another
problem) http://bugzilla.mozilla.org/showattachment.cgi?attach_id=42502 from bug
73865.
The new outliner frames the message area, leaving the scrollbar area outside,
even when not present. This new look may have the meaning of "this is the
intended behavior". A feature, not bug?
Reporter | ||
Comment 11•23 years ago
|
||
It's not intended because when you resize the window or the splitter, the border
snaps to the right edge like it's supposed to. It's acting as if there was a
scrollbar there, the size was calculated based on it, and then the scrollbar was
removed when the code realizes that it's not needed - but the size isn't
recalculated, thus leaving the border in the wrong place. A window resizes
causes a recalculation of the size. This time, the scrollbar is gone when this
happens so the border is drawn in the correct place.
Comment 12•23 years ago
|
||
When I resize the window, the space for the scrollbar stays there. At least for
recent 0.9.2 branch builds (WindowsME).
Reporter | ||
Comment 13•23 years ago
|
||
Putting back "bug 93101 blocks 92997" where it belongs. (was removed by the
termporary closing of this bug)
Blocks: advocacybugs
Reporter | ||
Comment 15•23 years ago
|
||
This seems to be a duplicate of bug 80834.
Reporter | ||
Updated•23 years ago
|
No longer blocks: advocacybugs
Comment 16•23 years ago
|
||
*** This bug has been marked as a duplicate of 80834 ***
Status: NEW → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: nobody → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•