Spin-off from #1465948-26: [meta] Drop some IE8 coddling from Drupal core.
Comment from Dries:
At the end of the day, we have a lot of work ahead of us to improve the user experience of Drupal. Making that progress is more important than trying to optimize for IE8. I'm comfortable with a single-column layout for IE8 users, especially if that means we see velocity improvements elsewhere in the project.
Noteworthy comment from jessebeach earlier in that issue:
Serving a single-column layout to IE8 is perfectly acceptable as long as the interface is usable. To say that a single-column layout is sub-optimal is to say that our mobile design will be sub-optimal (this assumes that the single column layout will be the primary layout on mobile devices). Rather than make exception for IE8 in core, I'd rather see us make the mobile experience so killer, that interacting with Drupal through a single column layout in IE8 will be completely acceptable. And if folks want a more complex layout, they can install one of many free, alternative, modern browsers on their system.
And I would add that for websites not convinced by the above argument, they can look to contrib for Respond.js, IE8-specific CSS additions to core themes, IE8-optimized contrib themes, etc.
Comment | File | Size | Author |
---|---|---|---|
#6 | IE8-no-patch-front.png | 119.5 KB | nod_ |
#6 | IE8-no-patch-node-edit.png | 70.82 KB | nod_ |
#6 | IE8-patch-front.png | 113.81 KB | nod_ |
#6 | IE8-patch-node-edit.png | 68.76 KB | nod_ |
#5 | no-ie-special-layout.patch | 2.04 KB | effulgentsia |
Comments
Comment #1
Crell CreditAttribution: Crell commentedThis is already marked RTBC, so I don't know if it needs comments, but register me as very +1. :-) IE 8 marketshare is only going to decline. This also, really, only affects core themes; if someone making a custom theme wants to support IE 8 with multi-column layouts, more power to 'em. That's their business and there's plenty of ways to do that. Core doesn't need that grief.
Forward!
Comment #2
ruplThis sounds great! I already have a D8 branch of respond.js module available for people that need it.
Comment #3
chx CreditAttribution: chx commentedIt doesn't worth bothering with stellar IE support. If it works to some extent, so be it.
Comment #4
kristiaanvandeneyndeHear hear
Comment #5
effulgentsia CreditAttribution: effulgentsia commentedAlrighty, let's take this from a policy issue to a patch. Someone with access to an IE8 environment, please attach some screenshots of what a couple pages look like in Stark (e.g., a node page to anon and a node edit page to an admin and whatever else you think is worth having people look at as part of reviewing this).
Comment #6
nod_Well, there is no more sidebar, that's what was expected.
I'd RTBC it but i'll let someone else do that.
Comment #7
nod_Actually that's very straightforward. works for me.
Comment #8
effulgentsia CreditAttribution: effulgentsia commentedBy the relative size differences of the scrollbars in the before and after, I'm assuming the sidebar is simply below the content?
Comment #9
nod_indeed.
Sorry about that, I kinda suck at screenshots.
Comment #10
jessebeach CreditAttribution: jessebeach commentedLovely.
The .fieldset-legend CSS for IE8 in Seven seems necessary for content access. The patch above is a great start.
Comment #11
Dries CreditAttribution: Dries commentedGreat. Committed to 8.x. And it feels great too. ;-)
Comment #12
chx CreditAttribution: chx commentedSingle column! Single column! Sorry. Couldn't resist.
Comment #13
JohnAlbinyay!
Comment #15
tim.plunkettCottser pointed out that http://drupal.org/core-gates states that markup, CSS, or JS fixes should be "tested in the browsers Drupal core currently support[s]".
Upon further inspection, the only pages we could find were http://drupal.org/node/61509 and http://drupal.org/node/367318. Which are both very out of date.
Also, unlike http://drupal.org/node/1569578, this never got a change notice.
Comment #16
tim.plunkettRelated: #1030090: Document our browser support list
Comment #17
jessebeach CreditAttribution: jessebeach commentedI'm not sure how much sense it makes any more to list target browsers. We need to mention the split at IE 8/9 in terms of complex presentation and style. Otherwise, any other browsers will be 3 versions ahead of anything we specify within a year. Chrome by 5 or 6 versions most likely.
Comment #18
nod_draft for the notice: http://drupal.org/node/1722502
Comment #20
tim.plunkettGood enough for me.
Comment #22
xjmComment #23
xjmComment #23.0
xjmInlined comment from Dries