Browse files

We don't do rems.

  • Loading branch information...
1 parent 6d48243 commit 6ea466068ff10d613b3faf462797d517a4c169cc @bradwright bradwright committed Jul 3, 2012
Showing with 6 additions and 20 deletions.
  1. +6 −20
@@ -9,13 +9,13 @@
display: block;
position: relative;
- top: 0; left: 2.4rem;
+ top: 0; left: 2.4em;
- width: 40rem; height: 60rem;
+ width: 40em; height: 60em;
margin: 0 auto;
- padding: 2rem 4rem 6rem 2rem;
+ padding: 2em 4em 6em 2em;
- font-size: 1.9rem; line-height: 2.5rem;
+ font-size: 1.9em; line-height: 2.5em;
text-decoration: underline;
color: #333;
@@ -59,20 +59,6 @@ For example:
(stolen from
-## REM sizing - why?
-At the moment the Citizen site uses em-based styles, where the font-sizes are calculated in relation to contextual em-sizing set on parent dom elements. This means that we have to calculate new em-sizes for every different dom context, which has a negative effect on code reuse and design consistency.
-To improve this, we're changing the core font-size on the HTML element from 100% to 62.5% (10px), which will allow new styles to utilise simple rem/px font-sizes, e.g.
-element {
- font-size: 16px;
- font-size: 1.6rem;
-rems are very similar to ems, except that they ignore dom context entirely and size relative to font-size set on the HMTL element. The px are a fallback for older browsers that don't support rem.
-In order to preserve the existing typography, the font-size is boosted back up again on the BODY element (which the rems will ignore).
+## REM sizing - why not?
+Because [IE6, 7, and 8]( don't support them, and mixing pixels with rems to get cross browser support is too much redundant code.

0 comments on commit 6ea4660

Please sign in to comment.