Loader garbage collection causes IE to request script with null src.

[zombeerose]

REQUIRED INFORMATION

Ext version tested:

• Ext 4.1.1

Browser versions tested against:

• IE8
• IE9

DOCTYPE tested against:

• Strict

Description:

• When performing garbage collection of async-loaded scripts, the Loader assigns null to every property of the script tag. By doing so, Internet Explorer will attempt to reload the script when the "src" property is reassigned. This leads to an unnecessary server request and 404 response for a "/null" uri. See image at bottom.
• It also appears that IE will attempt to reload the script when other properties are assigned. I did not identify which properties those are though.

Steps to reproduce the problem:

• Run the code in IE.
• Examine the Network requests.
• Change "garbageCollect" to false then repeat previous steps.

The result that was expected:

• Performing GC should not lead to extra/invalid network requests.

The result that occurs instead:

• GC causes a script with a "null" src to be requested.

Test Case:

    Ext.Loader.setConfig({
        disableCaching: true,
        enabled: true,
        garbageCollect: true,
        paths: {
            'Ext':           '/extjs/ext/src'
        },
        preserveScripts: false
    });

    Ext.require('Ext.data.SortTypes'); //super small class with few dependencies

HELPFUL INFORMATION

Additional CSS used:

• only default ext-all.css

Operating System:

• Win7

Screen Shot:
IE9 Network monitoring...notice the URL requesting /null
ie_null_url.jpg

[mitchellsimoens]

This has been fixed for 4.1.2