internet explorer complains about secure and nonsecure content inside a page
delivered by https
-----------------------------------------------------------------------------------------------
Key: WICKET-523
URL: https://issues.apache.org/jira/browse/WICKET-523
Project: Wicket
Issue Type: Bug
Components: wicket
Reporter: Peter Ertl
Priority: Blocker
Sorry,
maybe 'blocker' is too much for this issue but this will make parts of wicket
unusable on a HTTPS site using Internet Explorer (still most-used browser
though it sucks)...
The problem comes from code in wicket-event.js:
} else if (document.readyState &&
Wicket.Browser.isIE()) {
// internet explorer - use script with defer
attribute
document.write("<script id=ie_ready defer
src=javascript:void(0)><\/script>");
document.getElementById('ie_ready').onreadystatechange = function() {
if (this.readyState == 'complete')
domReady();
};
} else {
more precisely this line
document.write("<script id=ie_ready defer
src=javascript:void(0)><\/script>");
This causes internet explorer to complain about having secure and nonsecure
content in a https page.
Big alert window on each page render! *aargh*
this effectively means you can not use HTTPS pages with wicket on internet
explorer once you use the domReady event
(except if you don't care having a big error message on each page :-(
Did I mention that IE really sucks bad?
It happens on IE6 and IE7 here
the issue is identical to a ticket I found in mootools:
http://dev.mootools.net/ticket/139
the fix is easy (according to the mootools ticket)
replace:
document.write("<script id=ie_ready defer
src=javascript:void(0)><\/script>");
with
document.write("<script id='ie_ready' defer src='://0'><\/script>");
Looks really strange (://0) but works...
After changing that in my local tests the IE error message was gone and dom
ready handlers still worked
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
