User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy) Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy) The current hierarchical list view is not a good way to display the DOM tree. With less complex documents it is fine, however as the depth of the document increases it becomes exceedingly hard to navigate. Reproducible: Always Steps to Reproduce: 1. Open a deeply nested document in the DOMI (ie. Firefox) 2. Navigate to a node deep in the tree (ie. Tabbrowser documents) Actual Results: These nodes that are nested to a certain level are not viewable.
I suggest changing the DOM view to be more like that used in Firebug and Safari, this coupled with being able to filter the view (by CSS or Xpath selectors) will make this far more productive. This should also fix bug 112832
Comment on attachment 248211 [details] Screenshot of proposed filtered view random text boxes with no hints and no verbs other than clear are not remotely accessible. mo:a-
Attachment #248211 - Flags: review-
Created attachment 248235 [details] Updated view with hint text I think filtering by Xpath is important as well, so having a dropdown box to select what to filter by is probably going to be needed.
fyi - the only way this is going to get anywhere is if you make a bug for each feature, and submit patches from the trunk version of the code. Unzipping your xpi shows code that appears to be from the 1.8(.0)? branch. A lot of stuff has happened with the DOM Inspector since those branched, so the code may or may not look like that of the 1.8(.0)? branch.
Yeah I know, I've started working on it on the trunk. What do you think about it as a proof of concept? Are there features that I may not be thinking about that I'm removing?
(In reply to comment #7) > Yeah I know, I've started working on it on the trunk. What do you think about > it as a proof of concept? Are there features that I may not be thinking about > that I'm removing? Personally, I don't care for the firebug interface (displaying the html), and I'm fairly certain timeless doesn't either. However, the filtering is a neat idea that I like, and we have an xpath bug already open somewhere. Also, I'm not sure how accessible the firebug interface is, and it has to be.
(In reply to comment #8) > Also, I'm not sure how accessible the firebug interface is, and it has to be. I can't see any reason for it not to be accessible, keyboard navigation will be easy to hook in, screen readers should be able to access any text. I can see a problem with the use of colours, though there isn't a reliance on them. Being able to modify the font sizes should also help with it's accessibility. Is there anything else I'm not aware of?
Assignee: dom-inspector → nobody
QA Contact: timeless → dom-inspector
I'm changing the title here to reflect what it seems the scope for this bug is considering comment 6 and that we already have multiple XPath bugs on file. To anyone interested, take care of the XPath hinting in bug 425264.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: DOM View is cluttered and difficult to navigate especially in larger documents → Offer a Firebug-like view for the DOM Nodes tree
You need to log in before you can comment on or make changes to this bug.