Well, I can't say I have done an exhaustive check.
I do know that JQuery is planning to bifurcate - the current version is
1.8, and there will be a 1.9 series and 2.0 series with similar
functionality, but 1.9 will have support for "old" IE versions while 2.0
will drop this in order to improve performance.
http://blog.jquery.com/2012/06/28/jquery-core-version-1-9-and-beyond/
ExtJS 4 (a version that GeoExt has yet to support) still advertises IE6
support: http://www.sencha.com/products/extjs
I believe OpenLayers is still supporting IE6, but that project has a strong
culture of avoiding backwards incompatibility. Other browser mapping
libraries (I am thinking of PolyMaps in particular) seem to be doing
without IE6 support.
I will also point out http://www.ie6countdown.com/ which is in fact run by
the Internet Explorer team.
--
David Winslow
OpenGeo - http://opengeo.org/
On Tue, Oct 16, 2012 at 9:04 AM, Justin Deoliveira <[email protected]>wrote:
> I am fine with this. If it means fixing layout issues on newer IE versions
> then i think dropping IE6 is worth it. Out of curiosity what is the "life
> of support" for IE6 like on other projects?
>
> On Mon, Oct 15, 2012 at 2:12 PM, David Winslow <[email protected]>wrote:
>
>> Hi all,
>>
>> I've been looking a bit into how the web admin looks in Internet Explorer
>> after noting a few problems. I found some of the problems are actually
>> caused by our IE-specific styles - some exceptions that we made for IE6 are
>> actually causing IE7 and later to look incorrect. Rather than introduce
>> more conditional styles, I would like to know what folks think of just not
>> worrying about IE6 anymore? This is just CSS so things would still work in
>> IE6 as well as they do now, but there might be some layout issues (this
>> particular change affects table border widths.)
>>
>> I had meant to create a pull request, but since I had misconfigured git*
>> I actually pushed to the 2.2.x branch. If folks are opposed, I will revert.
>>
>> * I usually set up my repositories with 'origin' pointing to a shared
>> repo and 'dwins' pointing at my fork on github. Apparently I was lacking
>> in caffeine when I set this up the last time because I had both 'origin'
>> and 'dwins' pointing to [email protected]:geoserver/geoserver.git . Oops!
>>
>> --
>> David Winslow
>> OpenGeo - http://opengeo.org/
>>
>>
>> ------------------------------------------------------------------------------
>> Don't let slow site performance ruin your business. Deploy New Relic APM
>> Deploy New Relic app performance management and know exactly
>> what is happening inside your Ruby, Python, PHP, Java, and .NET app
>> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
>> http://p.sf.net/sfu/newrelic-dev2dev
>> _______________________________________________
>> Geoserver-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>>
>
>
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org
> Enterprise support for open source geospatial.
>
>
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
