Since my first post on Chromebug 0.5a1 netted a nice offer from davida, it’s time for a sober look at the new UI. Here’s a reminder of the top part of the UI:
window. Here is the top part of my context menu now:
Context Menu example for Chromebug 0.5a1 (top part)
At the top is
browser.xul, the window for Firefox. Below that are four Firebug windows. Two are the browsers Firebug uses for its main panel and side panel. Firebug’s HTML templates (domplates) fill these windows. Two are the inner and outer window for Firebug’s tracing console.
Below that we have the Error Console window (I usually run with -jsconsole) and then the hiddenWindow. All of these are
Selecting any of these will cause the lower part of the Chromebug UI to fill with content from the corresponding scope. For example, selecting
browser.xul will cause
- the HTML panel to show the elements of
browser.xul as rendered by Firefox;
- CSS will list the CSS files in
- Script panel will show the JS files loaded in to
- DOM will be document object for
(The Console and Net panels may show something, I don’t know yet).
browser.xul and in
Chromebug has some facility to help with these issues. Next time we’ll look into these, as well as ponder the contexts I cropped off the bottom of the menu. If you want to play in the mean time you can try Chromebug 0.5a1 (you also need Firebug 1.4a12).