Changes between Version 1 and Version 2 of Ticket #22044, comment 33
- Timestamp:
- 10/02/2012 10:29:09 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #22044, comment 33
v1 v2 1 On the reasoning why IE8 support matters, keep in mind that while most North Americans and Western Europeans have moved on from IE8, the rest of the world is stuck with the older browsers for economical reasons. The upgrade from XP to Windows 7 (and soon Windows 8) is prohibitively expensive for many individuals and companies and for this reason they are stuck with IE8. Because WordPress is a world wide application with a world wide reach, the world wide end-user should be provided with as good of an experience as possible.1 On the reasoning why IE8 support matters, keep in mind that while most North Americans and Western Europeans have moved on from IE8, much of the rest of the world is stuck with the older browsers for economical reasons. The upgrade from XP to Windows 7 (and soon Windows 8) is prohibitively expensive for many individuals and companies and for this reason they are stuck with IE8. Because WordPress is a world wide application with a world wide reach, the world wide end-user should be provided with as good of an experience as possible. 2 2 3 3 The main issue here is the decision to make the mobile menu default and placing the 'standard' menu in media queries. This makes sense if you take a mobile-first approach, but it is non-standard and against best practice scenarios. When advanced features like this are included in a theme, they should be added as progressive enhancements, i.e. the mobile menu should be added for browsers that can handle it while the 'regular' menu is served up for the rest.