Mozilla

DOM Inspector 2.0.1

I’ve just released DOM Inspector 2.0.1. This contains a number of stability and UI fixes. This is available on AMO, but you should automatically receive the update.

Tags DOM Inspector, Firefox, Mozilla, release, SeaMonkey

By Shawn Wilsher

The man behind the site.

View Archive

8 replies on “DOM Inspector 2.0.1”

2.0.1 does not appear to be compatible with Firefox 3.0.3. When trying to inspect a page, the plugin launches, but it has a blank screen. Is there a newer development version available somewhere that we can try out?

@Ry

I’ll try to take a look today, but I’m unaware of any issues with it :/

One of the user reviews for the plugin’s page (https://addons.mozilla.org/en-US/firefox/addon/6622) reports the same problem. I tried doing a full uninstall/reinstall of my FF3, immediately followed by adding the Dom Inspector. Unfortunately I still had no luck. Thanks for taking a look.

@Ry

It appears to be working just fine for me on Firefox 3.0.3. I’m not sure what to tell you :(

Some problem here.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

I hope you can resolve this I miss the functionality.

Thanks.

I’ve also noticed a bug with Dom Inspector on Firefox 3.0.3. Basically, if you try to expand any collection like childNodes, links, images, or forms. It will only expand if the length property for that object equals zero. Had the same problem on both Vista and XP with Firefox 3.0.3

Hi Shawn,

Apparently the DOM inspector no longer blinks the selected element in FF 3.0, are you seeing this behavior? 2.0 the element always blinked.

Thanks,

Rusty

Hi,

Thanks for your hard work. I’m experiencing problems similar to what was mentioned above – I cannot highlight a DOM tree element by clicking on it.

When I choose Select Element By Click, it only works sporadically (works = auto selects the clicked item in the DOM tree). For example – on google.com, it will only work with the big image but not with the search box. I really miss this great functionality, any chance of fixing this issue?

Thanks,
Daniel

Comments are closed.