Rated 5 out of 5 stars

by dcphosting_services on March 24, 2009 · permalink

I have used the DOM Inspector for some time now and would like to say Thank You for this plug-in. It has been a blessing to me as I have evolved in my role as a web developer.

Like the previous commenter, there was a time I didn't know the meaning DOM (Document Object Model). I can trace my computer roots back 1973 as a sophomore taking a Fortran class. I may not have owned my own company where I can hire people to KNOW things for me so I have learned to LEARN before criticizing somebody about something of which I know nothing. I did not know what DOM was until I needed/wanted to learn about this web developing related subject.

I would like to report a personal achievement using the DOM Inspector in straightening out the various javascript used on a client's site. I recently have been able to correct all the errors from "not well written code", "conflicting functions and variables", as well as the elimination of "depreciated code aspects".

The DOM Inspector has many more features than I use. This may be the result of my knowledge diffency rather than an overkill on the author's part. I sometimes use some of the features for possibly other than intended reasons... Like by turning image paths on it is quite easy to see if that ebay auction is stealing a client's image bandwidth or say when visiting paypal.com if the image paths are from paypal.com (bad) or a local directory (better - but not "good", could be lifted.). If I am suspecious enough I'll even check if the javascipt is changing the link names or desitinations. I also use DOM Inspector to examine other web sites. I like to browse the site structure of both sites I like and that of those I don't like. I like to see what of where I can improve as well as what things to avoid. Thank You for this plug-in.