Kendo initialization scripts in body interfere with other libraries

 Currently Kendo UI widgets output their JavaScript in a $(function() {} ) block. This means that it will execute when the DOM ready event is raised. If you want to modify the DOM before that you can attach your handler before the declaration of the Kendo widgets:

 Can you exclude the <script> elements when moving the DOM nodes? If they have been executed already you can just remove them before performing the move:

 We currently don't have plans to revive the ScriptRegistrar. We could probably however investigate if we can use Razor sections to output the script in a user specified location. I am not sure if this is even possible but is worth checking.

 Do you mind sharing with us how you achieved rendering of the script at the bottom of your page? 

Thanks for the idea. We have played around with it and seems to came up with a possible improvement for the described scenario. The idea is to have a  per widget
setting  which  will "defer" the rendering of initialization scripts. Similar to the following:

• Initialization scripts stay where they are (just after the elements they initialize), hence not being deferred to the end of the page
• Deferring should be the default behavior (or some other way)

• @Html.Kendo().DeferredScripts() gets called more than once (ex. on View and then later on Layout) with the first @Html.Kendo().DeferredScripts() called after the required resources are available (jQuery/Kendo etc.)
• Deferred scripts are never output:
  1. Partial View is returned from Action Method with no @Html.Kendo().DeferredScripts() present
  2. Scripts are deferred after calling @Html.Kendo().DeferredScripts() (which means the response gets sent without the deferred scripts included)

1. Assign an arbitrary identifier to the request & add a script reference (ex. ~/deferred.axd?key=) where the deferred scripts should be collected
2. Collect all the deferred scripts.
3. On a Http Handler EndRequest add the deferred scripts to the cache using the arbitrary identifier.
4. The browser will initiate a request to fetch the deferred scripts, whereafter the cache entry can be removed.

Thanks for the feedback.
If I understood correctly the later approach, you should be able to use it with current version of KendoUI for ASP.NET MVC without any modifications of the code.
However, we think that the DeferredScripts approach is still applicable solution in most of the scenarios. It also does not require inclusion of two more scripts on the page, which also is error prone.

• is it possible to bundle all the controls initialization in one single jQuery initialization function instead of a call for each of the deferred controls?
• if not, there is plans to implement such thing?
• Eventually is a contribution accepted?

I'm afraid that this is currently not possible. However, we may consider implementing such option for future version of the KendoUI for ASP.NET MVC base on the user interest. Therefore, you may consider posting your idea in our user voice.

Feel free to share your code with us here if you like.

Thanks for the suggestion. We have added such option to DeferredScripts method. It will be available with the Q1 2013 release of KendoUI, which is scheduled for the second half of March.