Opera, Konqueror and Safari have issues with the default document builder (aka
IFrameBuilder) approach that prevent them from running the test suites.  The
proposed modification will allow them to them to run the test suite.

Currently, when the test is generated an element like:

<iframe name="doc" onload="loadComplete()"></iframe>

is added to the generated test HTML file (for example, hc_attrname.html) for
each document to be loaded (for example, hc_staff.html).

In setUpPage() which prepares the test to run, a line like:

docsLoaded += preload(this.doc, "doc", "hc_staff");

which causes something like

document.doc.document.location.href = "files/hc_staff.html";

to set the location of the iframe's document and initiate loading the test
document.  The completion of the load is expected to cause the loadComplete()
method (specified using the onload attribute on the iframe element) to be executed.

As far as I can tell, the document is loaded in the iframe and the problem is a
failure of loadComplete() to be called.  However attempts to provide a failsafe
timeout that would call loadComplete() sometime after the expected load
completion was not successful.

I was able to get Opera, Konqueror and Safari to run by statically encoding the
test document into the <iframe> element.  Basically, generating

<iframe name="doc" src="files/hc_staff.html"></iframe>

and modifying the iframe loader to use this document. 

The behavior of Mozilla and Internet Explorer did not appear to be affected by
this change.  This would add an unnecessary HTML document load when running
other document builders (DOM3LS, MozillaXML, MSXML, etc), but should not
interfere with their results.