This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 183732 - Document outline (graphical tree) displays element nodes out of order
Summary: Document outline (graphical tree) displays element nodes out of order
Status: RESOLVED WORKSFORME
Alias: None
Product: web
Classification: Unclassified
Component: HTML Editor (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal (vote)
Assignee: Marek Fukala
URL:
Keywords: UI, USABILITY
Depends on:
Blocks:
 
Reported: 2010-04-08 20:03 UTC by Reiger
Modified: 2010-04-12 12:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Reiger 2010-04-08 20:03:11 UTC
The document outline viewer displays various element nodes out of order. The raw inheritance structure is correct, but the positioning of the elements (top to bottom) is off. 

This is an issue when editing big HTML or for that matter any SGML or XML document in which order is semantically relevant; because it means that you can no longer apply your own mental model of the document structure to use the outline editor for its primary purpose of document navigation/introspection.

For instance the following screenshot of a large-ish README html file shows how the <h1> element is off by 2 other elements: http://img641.imageshack.us/img641/6679/outlineoutoforder.png

Looking closer at the document reveals that the document outline editor is displaying these items “in random order” or “in alphabetical order” but rather that it has managed to display each element shifted by 2 positions, wrapping the last two elements around to appear as the first in the outline. (div id="license" is the bottom element in actual document order.)
Comment 1 Marek Fukala 2010-04-12 12:41:26 UTC
Works fine for me even in big complex files. Please attach a sample file where I can reproduce the issue and reopen this bug. Thanks