-
22 Jun 2012 2:25 AM #1
Ext.Loader getting negative pending files count in Firefox (doesn't fire onReady)
Ext.Loader getting negative pending files count in Firefox (doesn't fire onReady)
REQUIRED INFORMATIONExt version tested:
- Ext 4.1.0
- FF13 (firebug 1.9.2 installed)
- ____
- In a complex application (around 100 js files) Ext.Loader may fail to raise the onReady event after all files have loaded.
- FF seems to make duplicate requests for files, fetching a second time from the local FF cache :S
- Create a large project with lots of dependencies.
- Enable the Ext.Loader with disable cache to false.
- Load the page a few times.
- The page loads perfectly every time.
- More often than not the page will remain blank and no application code will execute.
Debugging already done:- Inspected the net inspector and can see two requests for some files. Added additional logging to Ext.Loader that shows it actually only requests once (it seems FF requests from the server and then again fetches from the local cache some time later). It seems that onFileLoaded is called multiple times because of this behaviour (checked this by adding logging in onFileLoaded).
- modify Ext.Loader.onFileLoaded handler (line 1002) to check whether the class file is already loaded. If it is already loaded, return immediately instead of updating counts.
- only default ext-all.css
- ________
- Win7 Ultmate
-
22 Jun 2012 7:53 PM #2
Can we get a test case for this? If you don't want to put your app up here you can email it to evan@sencha.com
Evan Trimboli
Sencha Developer
Twitter - @evantrimboli
Don't be afraid of the source code!
-
25 Jun 2012 12:42 AM #3
Hi Evan,
Thanks for getting back to me, unfortunately we are restricted from sending our main project code to non-customers. I will put together a test project for you in the coming days.
Luke
-
29 Jan 2013 2:50 AM #4
I exeprience this bug with FireFox 18.0.1 on Linux. Looks like Ext.Loader doesn't work properly in FF when you have a large project with complex folder structure.
Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format.


Reply With Quote