Make WordPress Core

Opened 4 years ago

Last modified 6 days ago

#18199 new enhancement

Deprecate IE7 in the Admin

Reported by: nacin Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Administration Keywords: needs-patch
Focuses: ui Cc:



Everyone hates IE7. It’s insecure. Let’s make it go away. Also, dropping IE6 didn’t give us much beyond goodwill, because most of the hacks we needed for IE6, we also need for IE7. So we could actually clean up our CSS a bit if we dropped IE7.

Change History (22)

comment:1 @azaozz4 years ago

Big plus from me :) However going through the various browser usage stats here: http://en.wikipedia.org/wiki/Usage_share_of_web_browsers it seems IE7 is at average 7-8% of all browsers used. Perhaps still a bit too high, may be better to keep it around till 3.4.

comment:2 @sbressler4 years ago

  • Cc sbressler@… added

comment:3 @ocean904 years ago

Related: #17232

comment:4 @andrewryno4 years ago

  • Cc andrewryno@… added

comment:5 @jane4 years ago

  • Milestone changed from 3.3 to Future Release

We agreed a bit ago that this was something we'd think about for 3.4, not 3.3. Punting for that reason.

comment:6 follow-up: @ocean904 years ago

  • Keywords needs-patch needs-testing 3.4-early added; 2nd-opinion removed

comment:7 in reply to: ↑ 6 @azaozz4 years ago

Replying to ocean90:

Agreed with "3.4-early" depending on the global usage numbers, don't think it would need a patch or testing though :)

comment:8 @solarissmoke4 years ago

  • Cc solaris.smoke@… added

comment:9 @Ipstenu4 years ago

  • Cc ipstenu@… added

comment:10 @kwight4 years ago

  • Cc kwight@… added

comment:11 @nacin4 years ago

  • Keywords 3.4-early removed
  • Type changed from task (blessed) to enhancement

comment:13 @ocean903 years ago

  • Milestone changed from Future Release to 3.6

IRC chat from today

nacin: I can pull some stats from browsehappy. Will take a week or two to collect.

The plan would be to leave any IE hacks (ie.css) for now but just no further support.

comment:15 @sunnyratilal3 years ago

  • Cc ratilal.sunny@… added

comment:16 @lkraav3 years ago

  • Cc leho@… added

comment:17 @nacin3 years ago

Based on a sample of data sent to http://api.wordpress.org/core/browse-happy/1.0/, collected over the last few days —

  • IE is 14.1%
  • IE7 is 2.0%
  • IE8 is 4.7%
  • IE9 is 6.1%

My thoughts: We haven't done a whole lot to make IE7 work in recent versions. In 3.5, the stuff we did for IE8 already got us 90% of the way there. In 3.4, we had the customizer require postMessage, and thus didn't support it for IE7. In 3.6, more work will be directly in the admin (versus a separate experience, like the media library and customizer), but once you do IE8, we're usually pretty close to IE7.

Our level of support for IE7 has been pretty simple: just make sure it degrades in a somewhat graceful manner. If gradients are busted, that's fine. Lack of support for alpha transparency doesn't bother us. Even just declining to show a feature in IE7 is fine. But it doesn't take much to ensure that we have no terribly broken interfaces with boxes floating off the screen. How much we actually fix up in IE7 should be a feature-by-feature call, and probably only after we've done the IE8 support.

We used to group IE7 with IE6, but it's also fair to group it with IE8. Both are fairly old browsers that have very similar quirks. It's why jQuery 2.0 is dropping (sans-shim) IE 6, 7, and 8, rather than just IE7 and older. Also, Windows XP is EOL come 2014, which kills the operating system base for IE8 and below, so we'll probably start to see enough shift by 2014 or 2015 to pretty much drop IE8 and below.

comment:19 @philiparthurmoore2 years ago

  • Cc philip@… added

comment:20 @zoonini2 years ago

  • Cc kathryn@… added

comment:22 @chriscct76 days ago

  • Keywords needs-patch added

I thought IE7 was deprecated in 3.3 or 3.4 but can't find any proof of that at the moment.

Note: See TracTickets for help on using tickets.