If you want to see the effect of script changes on the DOM (that is, you want to see the current document structure instead of the original HTML source) in firefox take a look at firebug. It shows live updates to the DOM and CSS (and allows you to change it), has a script-accessible javascript log (with stack traces), can evaluate user-entered javascript in the current page's context, logs XMLHTTP requests and more. It really is the most useful tool I know for javascript (and HTML) debugging.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to OT: debugging HTML DOM & Javascript (was: Re^2: Win32::IE::Mechanize not getting correct content) by Joost
in thread Win32::IE::Mechanize not getting correct content by cormanaz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.