Voting starts in March for the Drupal Association Board election.
Over the past decade, the general sentiment of web developers and clients has been visual fidelity to a common design across platforms. To be specific, a web site was expected to look the same on every platform. In the past couple years, as devices of all shapes and sizes flourish in the market, the expectation that a web site will maintain the same layout and appearance across devices is waning. In the coming years, desktop web experiences will become just another access point to information on the web. Drupal must evolve to support the flexible content presentation modes that web developers will demand of it in the not-too-distant future.
Given our focus in D8 on forward-looking technologies, devices and development techniques, we need to ask ourselves how much effort we should invest into support of older browsers such as Internet Explorer 6-8.
We must recognize that IE8 still holds a significant web traffic market share although this share has trended downward for years. IE8 market share fell below 13% in June 2012 (source). Even though XP users are getting updated to IE8 we can easily predict that from here to when Drupal 8 will reach its plateau of productivity (2014?) IE8 will have a marginal marketshare (considering mobile browser growth).
Considering that XP support will end April 2014 and Drupal 8 will be released August 2013 we can assume that by the time people will start to deploy D8 sites–in those scenarios where supporting old IT departments makes sense– (6-9 months after release?) XP will be almost dead and IE8 with it. (Vista supports IE9)
Eliminate layout and styling exceptions for IE8 in Drupal core.
- Remove IE specific stylesheets. We should have no IE specific stylesheets in core after this effort is completed.
- Drop microsoft vender properties such as filter for shadows and opacity. These destroy performance.
- Use @media queries to drive layout changes. Support for @media queries in IE8- can be achieved in contrib with tools like respond.js
- Native support for media queries (no need for respond.js)
- Native support for media (video and audio). Take a look at the amazing work going on here to introduce media support to Drupal8 (http://drupal.org/project/html5_media)
- Various useful selectors :first-child :last-child :nth-child (pure css striped table)
- multiple-backgrounds and other background properties
- border radius
- box shadow
- The envy of those stuck in a dark era
- Inner Joy