ie6 issue: blank.html required for DOMWindow plugin to work.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. On page load, run the following command, where "popup" is just a div
with some content.
jQuery.openDOMWindow({ 
  height:210,
  width:480,
  positionType:'absolute', 
  positionLeft:0,
  positionTop:0,
  positionType:'centered',
  windowSourceID:'#popup'http://code.google.com/hosting/settings
});

2. This works fine in all browsers. In ie6, however, it tacks on an iframe
with src="blank.html", which causes the browser to make a request for that
source.
3. Check server logs to find 404 response or, in our case, an exception.

Expected output is a lightbox with the content of the popup div. Actual
output is a lightbox plus a call to load server-side page "blank.html".
This causes a 404 in the best case, or a server-side exception in the worst
case.

Why is the blank.html needed? If it is required, then you should add some
documentation.

Original issue reported on code.google.com by yoni.bm...@gmail.com on 28 Jul 2009 at 9:04

[GoogleCodeExporter]

By the way, the version is unknown, since the file doesn't include a version. It
looks like the current trunk has the "src='blank.html'" on line 254:
http://code.google.com/p/jquery-swip/source/browse/trunk/jquery.DOMWindow.js

Original comment by yoni.bm...@gmail.com on 28 Jul 2009 at 9:08

[GoogleCodeExporter]

From my understanding is that sites that are running this on a secure HTTP 
requests
will get a popup notification in IE6 that will ask if you want to display the
unsecured elements on the page.

To fix this I've modified the src="blank.html" to be src="://0"

This is more of a hack for IE6 and will trick the browser into thinking it's a
secured request instead of an unsecured one.

Also this fixes flooding your logs with 404 errors.

Original comment by spfaf...@gmail.com on 2 Nov 2009 at 8:26

[GoogleCodeExporter]

Updating the code to use src="://0" did not work and was still producing 404 
errors. However, using src="about:blank" did work and did not throw any 404 
errors.

Original comment by jasonawi...@gmail.com on 7 Oct 2010 at 5:19