User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b5pre) Gecko/20100828 Firefox/4.0b5pre Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b5pre) Gecko/20100828 Firefox/4.0b5pre I've tried both DOM Inspector and the built-in Inspect in 4.0b5pre and both show do not show the internal details of menu items in the Add-ons Manager. The farthest the DOM tree opens is: richlistbox#addon-list.list -xul:scrollbox --xul:box.box-inherit.scrollbox-innerbox Reproducible: Always
Component: General → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: general → add-ons.manager
Version: unspecified → Trunk
Works fine for me with todays Minefield build and DOM Inspector 2.0.7 and 2.0.8. Please update your build and try again.
If the tool doesn't work then it is most likely a bug with the tool
Component: Add-ons Manager → Developer Tools
Product: Toolkit → Firefox
QA Contact: add-ons.manager → developer.tools
A follow up. I *can* inspect the individual add-on items using DOM Inspector and selecting them in the original Firefox window, but I cannot inspect them after loading them in the DOM Inspector "Preview" pane, and not in Firefox's Inspector (which has been dropped from 4.0 release anyway).
(In reply to comment #4) > I cannot inspect them after loading them in the DOM Inspector "Preview" > pane What do you mean? You mean by typing chrome URI into the location bar? If so, you shouldn't use that approach to inspect chrome. It's okay for inspecting web pages, but you should use the inspect menuitems in the File menu for when you want to inspect chrome. Using the devtools inspector to inspect XUL is a non-goal: https://wiki.mozilla.org/Firefox/Projects/Inspector#Non_Goals
I mean if I press the "Inspect" button on the right side of DOM Inspector, it reloads the page into a preview pane within DOM Inspector, from there I see the image I posted. However, if I do NOT press the "Inspect" button, and instead use the "Find a Node" button on the left side of DOM Inspector, and then highlight the area in the Addons Manager in the original Firefox window, it works. I have never attempted to type chrome URI into the location bar. I have always used the menus in DOM Inspector.
(In reply to comment #6) > I mean if I press the "Inspect" button on the right side of DOM Inspector ... > I have never attempted to type chrome URI into the location bar. I have always > used the menus in DOM Inspector. Don't do that when you're inspecting chrome, even if you don't manually type in the URI, e.g., if it's been filled in by previously using the menuitems. The location bar is really only there for inspecting arbitrary Web pages.
(In reply to comment #5) > you shouldn't use that approach to inspect chrome. (In reply to comment #7) > Don't do that when you're inspecting chrome I shouldn't be so sloppy with my words. When I'm saying "chrome" here, I mean real, true XUL, not just "anything located at a chrome URI". These should all be a-okay using the location bar, for example: chrome://global/content/viewSource.js chrome://global/content/bindings/tree.xml chrome://global/skin/icons/folder-item.png
Like I said, I've never typed anything into the DOMi location bar.
I also have the same/similar problem. How I can describe it is that the Add-ons Manager (about:addons) will not populate the list for extensions, appearance, and plugins. Let me know the next step on how I can furth aid developers on squashing this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
Verified with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b9pre) Gecko/20110102 Firefox/4.0b9pre ID:20110102030355
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.