[webkit-dev] W3C/NIST DOM Test Suites: Background Info

[Dave Hyatt]

Last I tested this onload did fire but did so with the wrong  
permissions.

dave

On Jun 18, 2005, at 9:52 PM, David D. Kilzer wrote:

> Bug 3609 filed for the "onload" event of an iframe element not firing.
>
>   http://bugzilla.opendarwin.org/show_bug.cgi?id=3609
>
> Dave
>
>
> On Jun 18, 2005, at 3:58 PM, Curt Arnold wrote:
>
>
>> [...]
>>
>> The ECMAScript productions come in a two flavors: A JSUnit-hosted  
>> (http://www.jsunit.net) test suite and a self-hosted test suites.   
>> The JSUnit test suite can be configured to use several different  
>> approaches to loading the test documents.  The most common for  
>> HTML browsers is the IFRAME loader which manipulates documents  
>> that are loaded by setting the src attribute on IFRAME elements  
>> that are embedded in the JSUnit test definition.  Unfortunately,  
>> Safari and Konqueror do not dispatch the "load" event to the  
>> document containing the IFRAME element which causes the JSUnit  
>> test suite to think that the test documents never load.
>>
>> The "self-hosted" productions were created to test implementations  
>> that could not run JSUnit, particularly the Palm OS browser  
>> (resource issues), ie:Mac Safari/Konqueror (the load event issue),  
>> and SVG browsers.  The self-hosted tests embed the test script  
>> into the test document and the script is run when the document  
>> completes loading and then change the document to indicate the  
>> success or failure of the test.  For example, the SVG tests turn  
>> into a green rectangle if pass, red if failed.  This approach  
>> allows most tests to be run in browsers that don't support JSUnit,  
>> however tests that depend on loading multiple documents can't be  
>> produced.
>>
>> [...]
>>
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at opendarwin.org
> http://www.opendarwin.org/mailman/listinfo/webkit-dev
>