DOM Inspector: Difference between revisions

Revision as of 01:20, 23 September 2005

There is considerable scope for improvement to the UI of the DOM Inspector.

ability to remember sessions
show inspector views as tabs instead of dropdown list items
autocomplete for the URL bar
consolidate mismatched UI items
inline search for computed style, etc. views with save ability
computed style etc saves scroll position
"Find a node to inspect by clicking on it" should work with the browser's toolbars (i.e you could click on the reload button and inspect it).
typing a url and hitting enter should inspect that url, without needing to click the "inspect" button
option to inspect the current window at startup instead of the current document
option to add "inspect this element" to right-click menu (like https://addons.mozilla.org/extensions/moreinfo.php?id=434)
The "find a node to inspect by id, tag, or attribute" ui could be changed to work like find-as-you-type
the trees can get really deep, and i constantly find myself trying to make the window bigger, and searching upward to find the parent of the node i'm looking at. not sure if there's a good way to address this?

...more later.

@@ Line 9: / Line 9: @@
 * inline search for computed style, etc. views with save ability
 * computed style etc saves scroll position
+* "Find a node to inspect by clicking on it" should work with the browser's toolbars (i.e you could click on the reload button and inspect it).
+* typing a url and hitting enter should inspect that url, without needing to click the "inspect" button
+* option to inspect the current window at startup instead of the current document
+* option to add "inspect this element" to right-click menu (like https://addons.mozilla.org/extensions/moreinfo.php?id=434)
+* The "find a node to inspect by id, tag, or attribute" ui could be changed to work like find-as-you-type
+* the trees can get really deep, and i constantly find myself trying to make the window bigger, and searching upward to find the parent of the node i'm looking at.  not sure if there's a good way to address this?
 ...more later.