[wp-trac] [WordPress Trac] #24858: Twenty Fourteen

[WordPress Trac]

#24858: Twenty Fourteen
----------------------------+------------------
 Reporter:  lancewillett    |       Owner:
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  3.8
Component:  Bundled Theme   |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by taupecat):

 Replying to [comment:37 emiluzelac]:
 > Should we remove all IE7 stuff from style.css, since the Theme isn't
 working on IE7 anyways? not sure if that's the plan and if it is all
 {{{*}}} hacks are no longer needed as well as:
 >
 > {{{{clip: rect(1px 1px 1px 1px); /* IE6, IE7 */} }}}
 >
 > Also, will the Theme support IE8 or this will be IE9+. Just asking what
 to test for that's all. Currently the Theme does not behave properly in
 IE7 nor IE8 :)
 >
 > Last question (more info only) Twenty Twelve uses rem, Twenty Thirteen
 does not and rem is back in for Twenty Fourteen, can someone shed some
 light please.
 >
 > Thanks!

 I had a convo with @nacin on #wordpress-dev last week about IE7 support.
 His theory was so long as it didn't return a blank page, then it was fine.
 As a themer, I don't think I necessarily agree with that opinion.  But if
 WordPress itself aims to continue supporting IE7, then I think the theme
 should too.

 On the flip side, @nacin said that IE7 fixes constituted about an hour per
 release cycle.  Theming is a totally different animal.  The effort that
 goes into making a theme IE7 compatible (not necessarily the same, mind
 you, but at least compatible) is considerably more than an hour.

 I think we need Lance's decision on whether Twenty Fourteen is going to
 support IE7 and by how much.  IE8, however, I think should be as fully
 supported as possible, since there are still a large number of Windows
 installations throughout the world limited to IE8 based on the fact that
 Windows XP still commands a high market share.

 Of course, by support, that could mean serving IE<9 users a simple print
 stylesheet. ;-)

 As for the rems issue, where to use rems vs. ems is a lot more subtle a
 distinction than I think most people give its full due.  There's a place
 for both in a theme.  However, if we're going to pick one OR the other,
 I'd say go with rems since in a large project, they provide the least
 guesswork as to what basis the font is being measured against.  But again,
 you have IE issues, and wherever you use a rem you need to have a pixel
 fallback in order to support IE<9.

 That's done easily enough via the use of a CSS preprocessor and mixins,
 but that's a whole other comment! :-D

--
Ticket URL: <http://core.trac.wordpress.org/ticket/24858#comment:38>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software