Execute JavaScript function after SharePoint is initialized

Question

I have a custom JS script which I load into SharePoint and have problems to get my init method executed after SP is finished with its own initializing.

_spBodyOnLoadFunctionNames

I tried the "official" way first and added my function name to the list of executed functions after body load with _spBodyOnLoadFunctionNames.push("myInitMethod"); but that does not fire on every page load, I can't rely on that.

ExecuteOrDelayUntilScriptLoaded

Then I tried to use ExecuteOrDelayUntilScriptLoaded(myInitMethod, "sp.js"); function but it does not fire on every page load either.

Both ways work - but not every time. I assume that my script is loaded sometimes before the SP is initialized. This happens mostly on Chrome but on IE as well.

How can I make sure that my script is executed when SP is ready?

---

Note: There is an interesting behaviour when the page is loaded and the SP object is not fully initialized (the registered functions in ExecuteOrDelayUntilScriptLoaded has not been called): As soon as I click on the "Navigate Up" anchor in the page (where you can see the hiarchy of the subsites) the following files gets loaded and my init function (registered in ExecuteOrDelayUntilScriptLoaded) gets called!

• core.debug.js
• sp.core.debug.js
• ScriptResx.ashx
• sp.ui.dialog.debug.js
• sp.runtime.debug.js
• sp.debug.js

So everything is fine after that click - but why not on pageload as it should be?

Answer 1

It seems that this behaviour is related to some issues between SP 2010 and Google Chrome - I don't have this issues on other browsers.

Answer 2

This is a timing issue that somehow occurs only on non-IE browsers. See http://withinsharepoint.com/archives/256 for an explanation and very easy fix.

Answer 3

Hey I came across your question when I was looking for a way to delay my JavaScript from loading until sp.js has.

The reason your code you provided works some of the time is because (some of the time) SharePoint doesn't initialize all of it's codebase. This is a big problem in Google Chrome, but can happen in other browsers (non-IE) as well. To work around that particular issue you can do something like this:

if (typeof(_spBodyOnLoadWrapper)!='undefined'){_spBodyOnLoadWrapper();}

I put mine inside of $(document).ready().

And thanks for answering my question :)