Safari Page Loaded

Hi MacBidder,

Maybe this post will help you out. Good Luck!
--Justin S.

I use this arrangement:

in the main script - to pause until the page is loaded:

If my page_loaded(50) ...

and then the subroutine:

on page loaded(timeoutvalue)
delay 5
tell application "Safari"
repeat with i from 1 to the timeout_value
If (do Javascript "document.readyState"in document 1) is "complete" then return true
delay 1
end repeat
end tell
return false
end page_loaded

This works most of the time, but I have observed problems when my PowerBook is overloaded - or there's heavy network activity - when it seems that the document readystate tests true halfway thru the actual page load. This is for no apparent reason other than these loads and almost seems as though Safari might be 'giving up' and changing the readystate precipitately! You could try testing for "loaded" as well to see if that helps.

Replying to you earlier set me thinking about this again, and I think I have the answer:

If you check for "complete" before the remote site has started to send data, it will test TRUE. So what I did was to use the JavaScript "document.title" as another condition. (Incidentally, if Safari shows "Untitled" in the Window, this tests as a null string "") As soon as the remote site starts to send, the loaded state will change from "complete" and the window title will have contents.

(In pseudocode: IF your window title is NOT "" AND your loaded state is "complete" THEN move on to the next step.)

Replying to you earlier set me thinking about this again, and I think I have the answer:

If you check for "complete" before the remote site has started to send data, it will test TRUE. So what I did was to use the JavaScript "document.title" as another condition. (Incidentally, if Safari shows "Untitled" in the Window, this tests as a null string "") As soon as the remote site starts to send, the loaded state will change from "complete" and the window title will have contents.

(In pseudocode: IF your window title is NOT "" AND your loaded state is "complete" THEN move on to the next step.)

It's a shame they named all pages the same. (I am glad Apple doesn't do it here, otherwise I would have problem with auto-logins!)

I think the only option that you have then is to put a sufficiently long delay at the beginning of the subroutine to ensure that the remote site has time to respond. Of course that's not a precise thing, and will not cope with all connection speeds, but it will at least prevent the original problem of which you complained.

Remember, however, that if you are starting from a blank page and loading the first of your site's pages, you will be able to use this trick to spot the conjunction of a page that is not entitled "" and has loaded.