When running selenium for IE6 a javscript error is produced when jQuery-1.3.2 is included into the html page.

Details below:

In revision 6081 of support.js

the following code was added:

87      // Figure out if the W3C box model works as expected
88      // document.body must exist before we can do this
89      jQuery(function(){
90              var div = document.createElement("div");
91              div.style.width = "1px";
92              div.style.paddingLeft = "1px";
93
94              document.body.appendChild( div );
95              jQuery.boxModel = jQuery.support.boxModel = div.offsetWidth === 2;
96              document.body.removeChild( div );
97      });

This causes an error as the bindReady function breaks for IE6 in selenium.

When jquery executes the check to see if the document is ready:

// If IE and not an iframe
// continually check to see if the document is ready
if ( document.documentElement.doScroll && window == window.top ) (function(){
	if ( jQuery.isReady ) return;

		try {
			// If IE is used, use the trick by Diego Perini
			// http://javascript.nwbox.com/IEContentLoaded/
			document.documentElement.doScroll("left");
		} catch( error ) {
			setTimeout( arguments.callee, 0 );
			return;
		}

		// and execute any waiting functions
		jQuery.ready();
	})();
}

The call to document.documentElement.doScroll("left") doesn't raise an error. This might have something to do with selenium running the page in an iframe, and because there is no error raised, jQuery.ready() is called.

I added the following code on my local copy to the try statement and it now works.

try {
   document.documentElement.doScroll("left");
   var div = document.createElement("div");
   document.body.appendChild( div );
   document.body.removeChild( div ).style.display = 'none';
}

The selenium version information is:

running Selenium RC and Selenium Core 1.0 beta 2, the latest release on the Selenium download page.

However, it also occurred in the latest release before 1.0 which was Selenium RC 0.9.2 and Selenium Core 0.8.3 I believe.

The thing of note is obviously that it's running in Selenium's "single window" mode (the default has changed in the latest version (1.0 beta 2) to be "multi window" mode), where it's injecting the html into the iframe then.

Other possibly secondary things of ntoe:

• It's using the Java client driver

• It runs on Selenium Grid (ver 1.0.3)

• We're using LoggingSelenium which is a wrapper for the actual underlying Selenium libs to log screenshots and stats.

To replicate it was just a simple html page that includes the latest jquery-1.3.2.js and then run selenium in single window mode for IE6 and open the page.

The javascript error that pops up pinpoints this line:

3205 document.body.appendChild( div );

and the error says "document.body is null or not an object"