I should agree with Vincent. The reason IE8 is still in use is mostly because it is the latest MS browser for Windows XP. I know that XP will be EoL very soon, but while MS has taken that decision, the current market share of Windows XP is still quite large. I hope the EoL will speed up a bit the migration process, but not enough for dropping IE8 now. It could be a project for the 7.x release if the regression of IE8 is confirmed.
While it requires a bit of adaptation, bootstrap 3 support IE8, so I do not see why we would need to stop supporting IE8 for the new skin. Obviously, the design under IE8 will be a bit degraded. Supporting IE8 does not prevent us from using latest HTML5/CSS3 features, if IE8 degrade nicely. And there is no real need to be responsive on IE8, since no mobile device use it. So I am currently -1 for this change. Thanks, PS: I am far more concerned by the JS conflict issue we have between Bootstrap, JQuery and Prototype. On Tue, Mar 11, 2014 at 3:31 PM, [email protected] <[email protected]>wrote: > -0 at this stage from me. IMO we need to first question our xwiki users > and do a more thorough survey to understand who’s using XWiki with IE8 and > how they’d feel if we dropped support for it. > > According to > http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar, > IE8 is one of the top IE versions used by users so it seems a bit early to > take a decision right now about this. > > Since XWiki is an Enterprise software it’s all the more important to > verify that Enterprises are ready to drop IE8 before taking that decision > IMO. > > Thanks > -Vincent > On 11 Mar 2014 at 15:13:04, Ecaterina Moraru (Valica) ([email protected]) > wrote: > > Hi devs, > > This mail is about voting to drop support for IE8 in 6.x cycle. > > The issue is more complicated, since according to our 'Browser Support > Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF, > Chrome (+ Safari5). > > IE8 was released in March 2009 (4 years ago) > IE9 - March 2011 (2 years ago) > IE10 - Sept 2012 (17 months ago) > IE11 - Oct 2013 (4 month ago) > > With the release of IE11 some companies also dropped their support for IE9, > so we should also adjust our support strategy by supporting newer browsers > (IE10, IE11) and dropping the support for old ones (IE8, IE9). > > According to Statcounter for the last 6 month period > http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-barthe > most popular IE browsers are IE10 (8.48%) and IE8 (7.98%). > > While the market share is not neglectable there is something you need to > consider: > In 6.x we want to add a new skin: Flamingo. Ideally this skin should be > responsive. In order to assure responsiveness we need media query support. > IE8 doesn't has support for media query natively, we would need Respond.js > [2] to enable it. > While this solution exist, 6.x will be ready at the end of 2014 when I > suspect the market share for IE8 will drop. > > Additional to not having media query support, there are other CSS3 > properties and HTML5 elements that are not fully supported by IE8 > (border-radius, box-shadow, transition, etc.). > > This is my +1 to drop support for IE8 in 6.x > > Thanks, > Caty > > [1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy > [2] https://github.com/scottjehl/Respond > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > -- Denis Gervalle SOFTEC sa - CEO _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
