The script tags should contain "defer" attribute. Resolution: You can set the LoadScriptsBeforeUI property of the script manager to false so that the scripts will render as late in the page as possible (just above the inline <script> that MS AJAX generates for the $create() statements). This will provide benefit nearly identical to the defer feature, but it does not risk breaking existing functionality. More information on the property: https://msdn.microsoft.com/en-us/library/system.web.ui.scriptmanager.loadscriptsbeforeui(v=vs.110).aspx
When it is not possible to load scripts/styles from CDN, the scripts and styles should be loaded from embedded resources. Please monitor this item as it was the original and has more votes: https://feedback.telerik.com/Project/108/Feedback/Details/119156-add-cdn-fallback-to-local-support-added-to-radscriptmanager-radstylesheetmanager
I hate the stupid asp script managers...they're so ghetto with the .axd files always hosing our yslow\pagespeed scores, etc. Since your focus is no on css3\html5\lightweight rendering can you guys not come up a better way to bundle your scripts such that they render properly cached to the footer...maybe take a dependancy for that on system.web.optimization or something? ...maybe some sort of requireJS integration or...? Please feel free to think out of the box instead of being stuck into the asp.net crapballs bloat framework.
Subresource Integrity is a fairly new security scheme for protecting against malicious script obtained from third-party source (CDNs). It requires that the script tag include a hash of the script content so the browser can verify that it has not been altered. Telerik controls generate a bunch of script tags for cloudfront.net. It would be swell if the script tags would include the extra attributes necessary to implement subresource integrity. Is this in the roadmap? Mozilla provides a security analysis tool which highlights this issue. Look at the results for telerik.com here -> https://observatory.mozilla.org/analyze/www.telerik.com. More info available on https://infosec.mozilla.org/guidelines/web_security#subresource-integrity https://www.w3.org/TR/SRI/
When you pull in BootStrap there are additional attributes such as 'crossorigin="anonymous" and integrity="...." ' How can these be added to Script Manager and CSS manager? Likewise, there would a separation between bootstraps layout and the skin that Telerik an provide. This gives the advantage of it being BootStrap compliant, but with all the skins that Telerik offer, making re-skinning easier. This is one of the biggest bug bares of designing a site with Telerik, is the post-production work on CSS by a third party, as its not 'standards compliant' by which they mean its not like a normal Bootstrap site that they are familiar with. Thanks Doug <link rel="stylesheet" href=https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7" crossorigin="anonymous"> <link rel="stylesheet" href=https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap-theme.min.css integrity="sha384-fLW2N01lMqjakBkx3l/M9EahuwpSfeNvV63J5ezn3uZzapT0u7EYsXMjQV+0En5r" crossorigin="anonymous"> <script src=https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js integrity="sha384-0mSbJDEHialfmuBBQP6A4Qrprq5OVfW37PRR3j5ELqxss1yVqOtnepnHVP9aJ7xS" crossorigin="anonymous"></script>
During penetration tests we have to let carry out we allways run into problems with version disclosures originating from the embedded scripts and the Telerik.Web.UI. To keep updates of the telerik components easy and to stay out of version incompatibilities we would like to keep using the embedded scripts. Atm this is even more unlucky because the still, or again, used JQuery version 1.12.4 is known to be vulnerable to Cross-site Scripting (XSS) attacks. Our request would now be to at least remove the version comments from the embedded script files and the exact version of the Telerik.Web.UI in the links created to the Webresource.axd.
Since JQuery is such a small addition to your assembly wouldn't it be nice if a developer could select what version to use. So as a property I'd like useEmbeddedJqueryVersion with enums of 1,2,3 or none. This should also give you feedback on what controls need updating.