Interviewed by CNN on 09/07/2011 16:56, JD told the world: > JD wrote: >> Upgrading to SM2.2 has disabled DOM Inspector 2.0.10pre. I can't seem to >> find a way to get a later version and I can't find it's install.rdf >> file. Any suggestions? >> > > I found the .xpi file for DOM Inspector here: > > https://addons.mozilla.org/en-Us/seamonkey/addon/dom-inspector-6622/ > > Had to edit the install.rdf file and then it installed in SM 2.2 without > a problem and I have my DOM Inspector back. > > I can't recall ever using the DOM Inspector so I guess my DOM hasn't > ever needed to be inspected? >
DOM Inspector is a bit of a propeller-head feature, but I use it now and then. Sometimes, I want to extract a bit of code from a complex page (for instance, I want an article from a news site, WITH all the formatting but WITHOUT all the site-added crap like ads, links to unrelated stories, site headers and footers and so on). The DOM inspector allows me to locate the relevant part by following the DOM tree until the content branch -- and then copy *only* the HTML for that branch. It's also useful when whatever content you want is dynamically-loaded by a script, and refuses to save locally for whatever reason -- since the DOM inspector analyzes the code *in memory*, *after* the scripts have done their job. Oh, and it also means that those "HTML encryption" tools you see companies selling around are no more than snake oil, since it allows you to look at the HTML code *after* decryption. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my car stereo. *Added by TagZilla 0.066.2 running on Seamonkey 2.1 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
