Comments on: Using window.onload over HTTPS http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/ Thu, 11 Mar 2010 15:40:45 +0000 http://wordpress.com/ hourly 1 By: The window.onload Problem Revisited « Out of Hanwell http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-270 The window.onload Problem Revisited « Out of Hanwell Thu, 20 Sep 2007 22:05:40 +0000 http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-270 [...] Update: Applying fixes for HTTPS. [...] [...] Update: Applying fixes for HTTPS. [...]

]]> By: Diego Perini [Visitor] http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-226 Diego Perini [Visitor] Sun, 30 Jul 2006 03:16:14 +0000 http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-226 From what they have in their docs: <q>The onactivate event fires before the onload event for any of the objects listed in the Applies To section.</q> The difference with IE4 is that while loading, the <code>document.activeElement</code> is set to be the BODY object instead of NULL like in IE 5 and later. However we will still have an "onbeforeactivate" if that still don't work in IE 4... Everything is bound to the FOCUS mechanism and I really tested that also the "onfocus" events are fired during the loading process on the window, on the document and on the body objects. From what they have in their docs: The onactivate event fires before the onload event for any of the objects listed in the Applies To section.

The difference with IE4 is that while loading, the document.activeElement is set to be the BODY object instead of NULL like in IE 5 and later.

However we will still have an “onbeforeactivate” if that still don’t work in IE 4…

Everything is bound to the FOCUS mechanism and I really tested that also the “onfocus” events are fired during the loading process on the window, on the document and on the body objects.

]]> By: Matthias Miller [Member] http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-225 Matthias Miller [Member] Sat, 29 Jul 2006 19:30:44 +0000 http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-225 Based on the MSDN documentation, I really like what I see. I'm eager to run a number of tests on it next week. Are you concerned about behavior in IE4? When does onactivate get fired for that version? Based on the MSDN documentation, I really like what I see. I’m eager to run a number of tests on it next week.

Are you concerned about behavior in IE4? When does onactivate get fired for that version?

]]> By: Diego Perini [Visitor] http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-224 Diego Perini [Visitor] Sat, 29 Jul 2006 17:36:44 +0000 http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-224 Try to replace the bit of code for IE with this in a setTimeout loop: <code> if (document.activeElement) { fire_event(); }</code> Or by using the related event: <code> document.attachEvent('onactivate', fire_event);</code> It worked like a charm for me and also fixes the Back Button problem. Please if you have a test case that does not work submit it. I can't believe it something so easy existed, but I tested and it works... Waiting for your confirmation tests... Try to replace the bit of code for IE with this in a setTimeout loop:

if (document.activeElement) { fire_event(); }

Or by using the related event:

document.attachEvent('onactivate', fire_event);

It worked like a charm for me and also fixes the Back Button problem.
Please if you have a test case that does not work submit it.

I can’t believe it something so easy existed, but I tested and it works…

Waiting for your confirmation tests…

]]> By: Matthias Miller [Member] http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-223 Matthias Miller [Member] Tue, 18 Jul 2006 04:57:57 +0000 http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-223 Pretty much agreed--I'm certainly glad for your testing here. The problem with Firefox attempt to resolve is that it the throbber keeps going until it times out, so the script needs to be written out for IE only. And meanwhile, I'm stubbornly holding out until the IE7 RC to see how they've fixed the URL resolution bug. :-) Pretty much agreed–I’m certainly glad for your testing here. The problem with Firefox attempt to resolve is that it the throbber keeps going until it times out, so the script needs to be written out for IE only.

And meanwhile, I’m stubbornly holding out until the IE7 RC to see how they’ve fixed the URL resolution bug. :-)

]]> By: Alistair Point [Visitor] http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-222 Alistair Point [Visitor] Mon, 17 Jul 2006 14:00:20 +0000 http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-222 Regarding your obvservation that Firefox tries to resolve src=//: - I'm sure you're right, but this code is only for IE anyway! Which means, by an infinitessimally pedantic margin, I think my solution wins for not returning anything at all. (not that any of this would have been possible without all your work anyway) Anyway... :) Regarding your obvservation that Firefox tries to resolve src=//: – I’m sure you’re right, but this code is only for IE anyway! Which means, by an infinitessimally pedantic margin, I think my solution wins for not returning anything at all.

(not that any of this would have been possible without all your work anyway)

Anyway… :)

]]> By: Alistair Potts [Visitor] http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-221 Alistair Potts [Visitor] Thu, 06 Jul 2006 14:17:35 +0000 http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-221 Well done, and for spotting that src=0 generates a request we don't want. You can save yourself a few bytes by doing src=//0. I have updated my test page: https://www.partyark.co.uk/html/ie7b3success.asp A Well done, and for spotting that src=0 generates a request we don’t want.

You can save yourself a few bytes by doing src=//0.

I have updated my test page: https://www.partyark.co.uk/html/ie7b3success.asp

A

]]> By: Matthias Miller [Member] http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-220 Matthias Miller [Member] Mon, 03 Jul 2006 09:06:15 +0000 http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-220 I don't think you even need to toggle between http: and https:. You can just always use https:. I don’t think you even need to toggle between http: and https:. You can just always use https:.

]]> By: Rob Cherny [Visitor] http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-219 Rob Cherny [Visitor] Mon, 03 Jul 2006 08:21:25 +0000 http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-219 Hmmm ... Looking at your latest of course, I guess the location.protocol test could toggle between http: and https: based on the test, and not have to rely on the external file again? Yeah. If I get some time I'll test that... Hmmm … Looking at your latest of course, I guess the location.protocol test could toggle between http: and https: based on the test, and not have to rely on the external file again?

Yeah. If I get some time I’ll test that…

]]> By: Rob Cherny [Visitor] http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-218 Rob Cherny [Visitor] Mon, 03 Jul 2006 08:15:24 +0000 http://blog.outofhanwell.com/2006/06/27/using-windowonload-over-https/#comment-218 Guys, I've updated my <a href="http://www.cherny.com/webdev/26/domloaded-object-literal-updated" rel="nofollow">Object Literal version</a> to address the following: allows multiple calls also (sorta) resolves the IE/HTTPS issue Let me know what you think. Guys, I’ve updated my Object Literal version to address the following:

allows multiple calls
also (sorta) resolves the IE/HTTPS issue

Let me know what you think.

]]>