For topics about current BETA or future releases, including feature requests.
Post Reply
User avatar
Rank V - Professional
Rank V - Professional
Posts: 370
Joined: Fri Feb 17, 2006 5:22 am
Location: Victoria BC Canada


Post by roedygr »

I am gradually being forced into using JavaScript against my will. One of the disadvantages is the generated HTML is both invisible and not validated.

Is there any way to see the generated code, or to get it validated? perhaps by inserting some dummy functions.s

User avatar
Albert Wiersch
Site Admin
Site Admin
Posts: 3494
Joined: Sat Dec 11, 2004 9:23 am
Location: Near Dallas, TX

Re: JavaScript

Post by Albert Wiersch »

This is a good question but I am not aware of any good solutions.

Perhaps you could also put any JavaScript generated HTML in a "textarea" element for copying and pasting into CSE HTML Validator... but this would obviously need some manual intervention.

User avatar
Rank VI - Professional
Rank VI - Professional
Posts: 721
Joined: Mon Dec 13, 2004 1:50 pm
Location: Tannhauser Gate

Re: JavaScript

Post by MikeGale »

This is along standing problem.

There are a number of partial solutions (some browsers only, might inject some "extras"...) which in their native form involve manual intervention.

In essence the raw source disappears when the browser builds a DOM. If you write good markup, the difference will be small. For those who write tag soup and rubbish markup, the changes can be significant as the browser fixes the errors. Potentially different browsers might interpret source and changes differently, though the diversity is disappearing

Anything you use will convert the DOM to a textual format.

Here's some solutions I got from a quick search on the web, no guarantees:

Viewing generated HTML. Some crude notes 2014/08/24 20:26:14, from a web survey, not tested or analysed, some are old, none is likely to work in all browsers.

  1. Try going to the HTML tab in IE developer tools and press the refresh icon (next to the save icon), it will show the latest DOM.
    F12 -> F5 -> Ctl-S
    (Load dev tool, refresh, Save as file.)
  2. Code:"")"text/plain", "").write(document.documentElement.outerHTML);
  1. In Firebug's HTML tab, right-click the root node and select "copy HTML". Then paste to a text editor.
  2. Bookmarklet: javascript: var win =; win.document.write('<html><head><title>Generated HTML of ' + location.href + '</title></head><pre>' + document.documentElement.innerHTML.replace(/&/g, '&').replace(/</g, '<') + '</pre></html>'); win.document.close(); void 0;
Generated Source Bookmarklet. ... ted_source


Javascript (for bookmarklets, URLBar...)
  1. javascript:alert(document.body.innerHTML)
  2. javascript:void("\"text/plain\");document.write(opener.document.body.parentNode.outerHTML)"))
Random links
  1. ... in-ie.html
  2. ... in-firefox
  3. ... t-explorer
I haven't dug into what the jQuery team does. Might be interesting.

A good solution would be to automate your selected suite of browsers and automatically write the content to dB, file etc. then analyse. This looked like hard work last time I investigated it, if you do it I'd appreciate some details of what you end up doing.

When I've done this sort of thing, it's manually and I analyse the content of captures with CSE. The captures go into a web site, with associated baggage like css, images etc. With many designs there is not one generated page (per web page) but several at different "stages" of the process.

You can compare source / capture of content on the wire (where server generates content) using diff tools (though formatting and casing of tags may need a little work).

Let me know how you go.

Post Reply