-
8 Feb 2010 1:28 PM #1Ext JS Premium Member
- Join Date
- Jan 2010
- Location
- Rotterdam, The Netherlands
- Posts
- 383
- Vote Rating
- 8
Smaller ExtJS without IE6 support
Smaller ExtJS without IE6 support
Google's annoucement about dropping support for IE6 got me thinking. How much smaller in size would Ext Core get if you would remove all code that's only needed for IE6 compatibility?
Or, is it too early for dropping IE6 support?
Or, are there other browser that costs more Ext code supporting it?
-
8 Feb 2010 1:40 PM #2
We have no intentions of dropping support for IE6 at this time.
All browsers have their own issues and our aim is to provide a foundation where developers don't need to worry about the browser being used.Aaron Conran
@aconran
Sencha Architect Development Team
-
8 Feb 2010 1:44 PM #3Ext JS Premium Member
- Join Date
- Jan 2010
- Location
- Rotterdam, The Netherlands
- Posts
- 383
- Vote Rating
- 8
I can imagine. You need to compete with other JS frameworks. When did Ext drop support for IE5.5(sp2)?
-
8 Feb 2010 2:22 PM #4
a quick grep of the source shows only one IE6 specific fix:
I don't think that Ext ever explicitly supported IE5.5.Code:// remove css image flicker if(isIE6){ try{ DOC.execCommand("BackgroundImageCache", false, true); }catch(e){} }
-
8 Feb 2010 2:28 PM #5
-
9 Feb 2010 5:09 AM #6
I hope that ExtJS will continue to support IE 6 for some time.
One of my customers still uses the IE 6 and there's no timeframe of changing that. Many huge companies still uses the IE 6 and the normal worker don't have the right to use another browser. This effect can be seens in the statistics as the usage of old browsers decreases on the evening and weekends when people uses their private computers.
-
9 Feb 2010 7:57 AM #7Ext JS Premium Member
- Join Date
- Jan 2010
- Location
- Rotterdam, The Netherlands
- Posts
- 383
- Vote Rating
- 8
I know, some clients of ours also use IE6. Still the discussion could be interesting depending on what reduction in code size for Ext js we are talking about. Is it 20%?
Consider this, why do 98% of your visitors need to experience a slower framework due to Ext js code to support a browser that the other 2% has. Why not only include the Ext js code needed to support IE6 when that's the browser visiting the Ext js based website?
Or am I being to theoretical about this one...
-
9 Feb 2010 8:56 AM #8Sencha - Community Support Team
- Join Date
- Mar 2007
- Location
- Frederick MD, NYC, DC
- Posts
- 16,169
- Vote Rating
- 28
As long as IE6 is listed as a supported browser, then I think most companies will continue to support it as well.

Jay Garcia @ModusJesus || Modus Create co-founder
Ext JS in Action author
Sencha Touch in Action author
Get in touch for Ext JS & Sencha Touch Touch Training
We are also working on Video-based Sencha Touch training: Check it out here.
-
9 Feb 2010 10:15 AM #9
-
9 Feb 2010 11:54 AM #10
Individual users often upgrade quickly to the latest and greatest, but within corporations (those whose IT departments have any wits about them, anyway), users do not have the power to change anything. Every unit is deployed in exactly the same way, from the same "mirror" DVD, which wipes the sucker clean and installs a brand new world on it. If there is no material advantage to "changing the mix," it probably won't change; maybe not for years.
And that is gonna be ExtJS's world, methinks.


Reply With Quote