There is a strong consensus for removing ie6 *FRONTEND* support out of core.
1) Major web project doesn't supprt IE6 anymore: all the google stuff (docs, youtube, ...). Even wordpress dropped IE6 support ;)
2) IE6 doesn't support css class chaining, this makes it hard to theme and has lead to some ugly css code.
3) IE6 usage dropped to +/- 1.5% in most countries. Globaly it is still 10% of the market mainly caused by China
4) Drupal 7 has crappy support for IE6 and nobody complained. The admin theme looks rly bad and I'm not even sure the overlay is working. Bartik looks also bad due to the transparant png.
5) Nobody cares about IE6 anyway when developing for drupal these days. This will lead to garbage css code and IE6 won't render correctly in the end.
We need committer feedback because we want the approval of Dries for this.
Summary of catch
The overall consensus on this thread has been for the following, as far as I understand it anyway:
- Once this is done, go back and refactor all everything that's not so much a hack but just very dated - use modern CSS selectors, remove redundant class names etc. Removing IE6 support is a pre-requisite to that. These are all follow-up tasks though.
- Do not yet remove IE6-specific code from FAPI (checkboxes, security)- it will be much harder if not impossible to make that work from contrib, and it looks like there will still be IE6 usage in countries like China and Japan when Drupal 8 is released, so that might be a Drupal 9 issue.
- IE7 has lower usage than IE6, however any decision on that is being punted to a follow-up issue since it could happen on a different schedule.
Everything is done
User interface changes
IE6 will be even more unusable
Original report by catch
This came up in the redesign group, but I don't think it's very relevant to that. Might be worth testing the water with a core issue though.
I don't know how much practical impact this would have in terms of D7 development, but something likemaybe have a different outcome depending on whether we support IE6 or not due to PNG transparency, also some cross-browser issues with jQuery and themes. So we could agree in principle to drop IE6 support in icons/js/themes, then on a per-case basis decide what exactly that means.
It seems in the spirit of PHP5.2 MySQL5 and PostgreSQL8, but probably a bit more contentious.
Of course individual sites can easily support IE6 even if core doesn't, by using iepngfix, or their own theme etc. We already have progressive enhancement in at least one place - sticky tableheaders simply don't work in IE6, so there's a precedent. Of course we don't know when D7 will be released, or to what extent IE6 will still be in play when that happens, so this might need to be 'postponed' and revisited when and if it's a practical barrier to improvements.
|PASSED: [[SimpleTest]]: [MySQL] 32,956 pass(es).|
|FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch code-reviewed3.patch. This may be a -p0 (old style) patch, which is no longer supported by the testbots.|
|PASSED: [[SimpleTest]]: [MySQL] 32,212 pass(es).|