This post is to let you know about our plan to fully drop widgets support for IE7 imminently, and a proposal to drop support for IE8 in January 2015. Please read on for details and caveats.
About 18 months ago we updated our browser support for Twitter for Websites widgets-js to drop IE6 and move IE7 into a “partially support” state (https://blog.twitter.com/2013/tfw-ie6-ie7-support). I’m updating today to let you know that we’re considering the next round of browser support updates.
Critically, we’ll be dropping full support for IE7 imminently: Usage across the web has now dropped well below a 1% level. This will happen some time next week (after Thanksgiving.) Just as when we dropped support for IE6, you’ll see widget embed codes remain in your pages, functioning as links and HTML quotes.
We’ve traditionally taken a conservative approach to our browser support: We don’t want to be the forcing factor on any of your own browser support decisions. But the make-up of the web has changed and is now made up of a much more diverse array of physical devices. Thus we are also strongly considering dropping support for Internet Explorer 8 much sooner: Doing so will allow us to make widgets-js smaller, which is important for performance in general, while also freeing up much needed development time to better support widgets on Android browsers and mobile in general, which is rapidly approaching 50% of all web usage.
The proposal is that we’ll stop rendering widgets in IE8 at the beginning of 2015; some time in January. As above, IE8 will continue to render the links and HTML quotes that are present in your pages. No content will disappear! However, we’re aware that this is a shift, so if this would cause a problem for you, or if you think a more aggressive deprecation strategy like this will conflict with your work, please let us know here.
I would say that we’re pretty adamant we’ll go ahead dropping IE8 (usage is also not high), but I’m keen to listen out for general cases that we should consider delaying for.