Why does JSLink code associated with a site column fail to render on first load of document library view, but renders successfully on page refresh?

Question

Bit stumped on this one, wonder if anyone can help?

I've created some JavaScript which is stored in the Style Library and referenced by the JSLink property of a site column. When I navigate to a document library that includes the site column in its default view, the JSLink code does not appear to fire (tested using the line that writes to the console).

When I refresh the page however, the JSLink code fires and the image link is rendered for each item in the view. Why doesn't this code fire on the initial page load, but only on page refreshes?

(function () {
var overrideCtx = {};
overrideCtx.Templates = {};
overrideCtx.Templates.Fields = {
    'SiteColumnInternalName': {
        'View': function (ctx) {
    // write to the console so we know whether or not the render code has run
    if (console != undefined) console.log("Render code hit");
            return "<a href='" + ctx.HttpRoot + "/_layouts/somefolder/somepage.aspx?List=" +
                    ctx.listName.replace('{', '').replace('}', '') + "&ID=" + ctx.CurrentItem.ID + "'>" +
                        "<img src='" + ctx.HttpRoot + "/Style%20Library/img/someimage.gif'/>" +
                    "</a>";
        }
    }
};    
SPClientTemplates.TemplateManager.RegisterTemplateOverrides(overrideCtx);})();

Answer 1

Check out how this JavaScript is run with the minimal download option enabled.

Take the code sample and replace the address at the bottom with where you placed the JSlink file and give it a spin.

http://code.msdn.microsoft.com/office/SharePoint-2013-Folder-661709eb

Answer 2

I found the answer in the following link: http://social.technet.microsoft.com/Forums/en-US/sharepointdevelopment/thread/ca160c8a-b814-45e8-a9e3-6a4a4d768efa

MS added an SPWeb scoped feature called 'Minimal Download Strategy' to SharePoint 2013 which appears to break JSLink rendering (except for on page refreshes). Disabling the feature fixed the JSLink rendering!