Follow-up from #1471382: Add IE-conditional classes to html.tpl.php.
The problem
We've dropped IE6 and IE7 support, however there is still code in core that only exists to serve IE6 and IE7.
Additionally there is discussion in #1465948: [meta] Drop some IE8 coddling from Drupal core about dropping IE8 support. Whether we do or not, we can isolate CSS hacks into specific conditionally loaded IE8 stylesheets so it's easier to remove later.
There is also markup in core that only exists for IE8, for example .odd and .even styles. Personally I think we could drop support for those now - they can be added back by js if people need to support them in contrib quite easily.
Remaining tasks
Identify as much code as possible in core that was written to support IE8 or lower, whether documented or not. Open issues to either:
- remove it
- move it to conditional stylesheets
- properly document it as removable when we drop support for IE8 (or introduce respond.js).
Current list
- #1645494: Allow core themes to display single-column on IE8: do not compensate for lack of media query support
- #1649780: Remove first/last/odd/even classes in favor of CSS3 pseudo selectors
- #1651270: Remove IE8-specific workaround for lack of CSS3 box-shadow support
- #1825236: Remove bgiframe jquery plugin
Comments
Comment #1
nod_There is at least one piece of code added to D8 js that deals with IEs before IE9: #1199774: toolbar layout error in IE
Might be others as well, tagging to keep on my watchlist.
Comment #2
JohnAlbinThis will improve every browser except IE8. Tagging as frontend performance.
Comment #3
dcmouyard CreditAttribution: dcmouyard commentedWe should add this to the CSS cleanup process: http://drupal.org/node/1089868
Comment #4
dcmouyard CreditAttribution: dcmouyard commentedcross post
Comment #5
klonosIf we moved them to a separate core module that did that, it would be easier to move that module out of core and in contrib when the time came. This way, we'd have some solution already available to point people to instead of telling them to wait for a contrib module to add back any functionality we've chosen to remove. At the same time, we could have a "phase" during D8 core development when this module would be disabled by default (before moved out of core). This seems like the perfect phase-out procedure to me, but I don't know how much extra work would be required though ...just thinking out loud.
Comment #6
xjmRelated: #1532996: [Policy, no patch] Strategy for dealing with javascript in IE6/7
Comment #7
effulgentsia CreditAttribution: effulgentsia commentedOpened an issue for just this: #1649780: Remove first/last/odd/even classes in favor of CSS3 pseudo selectors
Comment #8
effulgentsia CreditAttribution: effulgentsia commentedI added a "Current List" set of issues to the issue summary. Is there anything else needed to satisfy this meta issue? We still have an ie.css file for the Seven theme, but the contents of that currently looks pretty harmless to me.
Comment #9
kristiaanvandeneyndeThanks @catch and @effulgentsia for the summary.
It sums up #1465948: [meta] Drop some IE8 coddling from Drupal core nicely.
Comment #10
Andrew_Mallis CreditAttribution: Andrew_Mallis commentedThere are also jquery libraries to consider.
see: #1825236: Remove bgiframe jquery plugin
Comment #10.0
Andrew_Mallis CreditAttribution: Andrew_Mallis commentedAdded links to IE8 CSS removal issues
Comment #11
catch#1649780: Remove first/last/odd/even classes in favor of CSS3 pseudo selectors is the last known issue dealing with this. That blocks another issue, so I'm going to mark this one 'fixed' and I've bumped the other to major anyway.
If someone finds another hack hidden away somewhere we can open new issues for it.
Comment #12.0
(not verified) CreditAttribution: commentedadding deprecated jquery plugin task