Success! Looks like we've fixed this one. According to our records the fix was applied for
Ext JS Premium Member
Loader garbage collection causes IE to request script with null src.
Ext version tested:
Browser versions tested against:
DOCTYPE tested against:
Steps to reproduce the problem:
- 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.
The result that was expected:
- Run the code in IE.
- Examine the Network requests.
- Change "garbageCollect" to false then repeat previous steps.
The result that occurs instead:
- Performing GC should not lead to extra/invalid network requests.
- GC causes a script with a "null" src to be requested.
Ext.require('Ext.data.SortTypes'); //super small class with few dependencies
Additional CSS used:
IE9 Network monitoring...notice the URL requesting /null
This has been fixed for 4.1.2