jQuery 2.0, Google Apps, Basecamp and other web applications have dropped support for IE8. This issue discusses whether or not Drupal 8 should too.
- As a point of reference, IE8 is right now where IE6 was in about June 2010 and we made the decision around this time in D7's cycle to support IE6. It took another 2 years (until about June 2012) for IE6 to become a non-issue. 2 years from now is April 2015, and that's well within D8's life cycle. (@webchick in IRC && #42)
- IE's current marketshare of 10% is not a trivial percentage. That's one in every ten people. (#62)
- It's also a percentage likely to be much higher among content authors, who are also less likely to have control over their operating system/browser environment (#62).
- Those left on IE8 are likely to be governments & conservative companies (#3)
- Will we be losing users, contracts and site builds because of an IE8 requirement (#5)
- Can PC users install other browsers (#8)
- It’s going to be a lot harder for sites to add IE8 support than remove it (#44)
- What about content authors? (#54, #55, #62)
- Getting laughed at for dropping IE8 in (late) 2013
- Smaller jQuery, quicker mobile experience (#22)
- Speed up the core development process by removing an annoying browser to test against (#59)
- Google Apps dropped support in November 2012 (#2)
- In we decided to use CSS3 and media queries without worrying about IE8 not receiving those styles
- IE8 is continuing to lose market share (#2)... http://theie8countdown.com/ (#52)
- Windows XP extended support ends on 8th April 2014 (#2)
- Drupal 7 will still exist (#4) and supports IE6,7,8
- Chrome, Firefox and Opera are all available on Windows XP (#6)
- Can make IE8 behave as a no-js
- Contrib can provide IE8 support (#12,#17)
- It’s not just Google - Basecamp is dropping support (#30)
- Is it really worth all the extra work maintaining IE8 support in D8 (#49, #50)
- End-user, site admins and authors are different - IE8 experience isn't broken, it just isn't rich and interactive. (#53, #54)
- Pushing forward organizations stuck in the un-upgraded past (#80, #91, #98)
- Getting laughed at for still supporting IE8 in 2018
- Sheer amount of features not supported in IE8 (#61, #70) see http://caniuse.com/#compare=ie+8,ie+9 & http://kangax.github.io/es5-compat-table/
- We could ship both jQuery 2.x and 1.9 and allow users to switch (#32, #34)
- We must always support the baseline, no js, simple styling, clean markup experience because all responsive and progressive development starts at this baseline (#68)
A work in progress update to Drupal's Browser Requirements documentation
Here is an incomplete list of browsers that are known to work well with Drupal 8 core and support all of its features:
- Internet Explorer 9 and later
- Firefox 5 and later
- Opera 12 and later
- Safari 5.1 and later
- Google Chrome
Even among the above browsers, the level of standards compliance varies, and so there may be minor variations in site appearance.
- What is normally displayed in multiple columns might appear in a single column.
- Alignment, spacing, fonts, colors, and other visual cues might be missing or appear incorrectly.
- Productivity enhancing features such as drag and drop item reordering, WYSIWYG editing, contextual links, and hiding of form elements until they're needed, might not function.
However, all content can still be accessed and site operations can still be completed.
|#42||Screen Shot 2013-04-22 at 12.19.11 PM.png||129.62 KB||webchick|
|#42||Screen Shot 2013-04-22 at 12.24.18 PM.png||57.95 KB||webchick|
|#42||Screen Shot 2013-04-22 at 12.29.35 PM.png||42.98 KB||webchick|