Closed
Bug 180047
Opened 22 years ago
Closed 22 years ago
DOM Inspector tree view doesn't scroll sideways, it must instead be resized
Categories
(Other Applications :: DOM Inspector, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 112832
People
(Reporter: martin.thomson, Assigned: hewitt)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
As I get deeper into a document tree, the "nodeName" column in "Document - DOM
Nodes" section of the window gets wider and wider. The actual content is always
at the right, but this can be unviewable unless the column is resized.
It's not always possible to resize that column wide enough and still have room
for the other 7 columns in that part of the display plus the Object details
section. Not everyone has a 21" monitor like I do, and if I have problems, I'd
imagine it is worse for others.
Reproducible: Always
Steps to Reproduce:
1. Find a document with a deep tree
2. Ctrl+Shift+I
3. Select a part of that document that is deep in the tree
The problem is more pronounced if you inspect a window and then inspect a
document within that window.
Actual Results:
I couldn't see the tree for the column being too wide.
Expected Results:
Some method of scrolling should be implemented. At a minimum, if a deeply
nested element is selected, the Inspector should show that element by scrolling
the column sideways.
Ultimately, the document tree should have its own scrollable pane. The
additional information available for each element would then have to be
displayed in a separate part of the display. But this is not trivial.
Comment 1•22 years ago
|
||
*** This bug has been marked as a duplicate of 112832 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Core → Other Applications
Updated•17 years ago
|
QA Contact: timeless → dom-inspector
You need to log in
before you can comment on or make changes to this bug.
Description
•