Closed
Bug 95270
Opened 24 years ago
Closed 24 years ago
Preferences tree list does not always have scrollbar when expanded
Categories
(SeaMonkey :: Preferences, defect)
Tracking
(Not tracked)
People
(Reporter: dfenton, Assigned: samir_bugzilla)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; rv:0.9.3) Gecko/20010801
BuildID: 2001080110
When you expand more than one node, eventually the number of lines required
exceeds the vertical size of the listbox control, but a scrollbar does not
always appear.
Reproducible: Sometimes
Steps to Reproduce:
Starting at the top, expand each node in turn, from top to bottom.
Actual Results: When number of lines exceeds vertical space of listbox, bottom
lines are pushed out of the visible area of the listbox, but no scrollbar
appears. Navigation into the hidden items on the list is possible via moving the
selection with the arrow key (highly undesirable, since you're flying blind).
Expected Results: As soon as the number of lines needed exceeds the visible
area of the listbox, the scrollbar should appear, regardless of the order in
which the nodes are expanded or collapsed.
If you start from the bottom, most of the time the scrollbar appears as
expected. And once that happens, if you collapse all nodes and then start from
the top again, the scrollbar appears properly.
And sometimes after much futzing around with expanding/collapsing nodes, Mozilla
crashes (as it did the first time I tried posting this bug report!).
This may be an issue with Windows large fonts. My default resolution is 1024x768
with Large Fonts (125% standard size). The control should be checking the actual
size of the fonts, not the base size of the source font.
The concept of the control is flawed. It is a non-standard UI widget and very,
very slow to load the node details (it is slow in NS4.x, too). Also, the
behavior of the +/- signs in other treeview controls (such as the history
window) and the interaction with clicking/doubleclicking on the nodes is not as
a Windows user would expect. Why reinvent the wheel? It's only going to confuse
end users and require the solution of problems that have been solved long ago.
Comment 1•24 years ago
|
||
*** This bug has been marked as a duplicate of 59108 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•