Hi I'm having a problem since I upgraded to version 2015.3.1111.40. It seems that some external javascript tags are being moved from their position about half way up the head to the end of the head after the stylesheets are rendered. Unfortunately this is breaking javascript in the head that is trying to reference the scripts before they are defined.
Please see the pseudo code below:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head id="Head1"><title>
==========SCRIPT TAGS RENDERED HERE WITH VERSION 2015.2.729.40===============
<script type="text/javascript" src="client.ashx"></script>
<script type="text/javascript" src="/JS/CustomEvent.js"></script>
<script src="/JS/GlobalEvents.js" type="text/javascript"></script>
=============================================================================
<script type="text/javascript">
//JAVASCRIPT STUFF
</script>
<link href="/WebResource.axd?d=GeaE1XAZCbM2xElfdpakRWK9V6QS7AU3nicMeAJ5diojozmIVm1_p383miQXR21SID15m4fD4kpKk2qGqs7PBSKutB6vkDGmWUpRyxfTq3r3IS9j5B90EIspv7UqcD_itjnaxcLSVzL7F9U0bbAKJQ2&t=635827770660000000" type="text/css" rel="stylesheet" class="Telerik_stylesheet" />
<!-- MORE TELERIK WebResource.axd -->
============SCRIPT TAGS NOW RENDERED HERE WITH VERSION 2015.3.1111.40=========
<script type="text/javascript" src="client.ashx"></script>
<script type="text/javascript" src="/JS/CustomEvent.js"></script>
<script src="/JS/GlobalEvents.js" type="text/javascript"></script>
==============================================================================
</head>
This is the rendered version of the page, the source has a code block and a script block in the head which may have some bearing?
Hope somebody can help as this is a large project and we can't make it live until we fix things.
Kind regards
Alan
1 Answer, 1 is accepted
Hi Alan,
There is a known issue with script reordering in Q3 2015 SP1: http://www.telerik.com/forums/known-issues-and-important-changes#wulq_2byPEOQJ03sAduJYw.
It is fixed in internal builds in December, but since you need that in production I suggest the following:
- use Q3 2015 (2015.3.930) which is the previous version and does not have this issue.
- OR, use Q1 2016 (2016.1.113) which is the latest available version at the time of writing.
As usual, I would recommend upgrading to the latest.
Regards,
Telerik