Skip to main content

CSS line-height Units Explained

In Chris Coyier's recent article, "Fun with line-height!", he mentions that we often use unitless values for line-height so that it's proportional to the font size. This is only part of the story, and I was reminded of a Stack Overflow question that got me investigating more about how line-height worked with regards to the various CSS units.

If you're declaring the line-height on each element, you won't notice any difference. But if you're not crazy and using the first C of CSS (that's 'Cascading', by the way), then the inherited line-height might not work the way you expect.

Disclaimer: This is my understanding after doing some research and testing. I may not be completely correct.

TL;DR

When using a relative unit (em, %), the line-height is calculated based on the font size of the element where the line-height is defined. This line-height is then inherited, unchanged, by each of its descendants. So we end up with a line-height that is relative to the calculated font-size of some ancestor.

When using a unitless value for line-height, the line-height is recalculated for each descendant element based on its calculated font-size, and therefore always relative to the font-size of that element.

Types of Units

There are three different types of units we can use here:

Absolute
px, in, cm, mm, pt, pc
The size of these units is an absolute measurement. So no matter what context, 3px always == 3px.
Relative
em, %
These units are relative to the font-size of their containers, or browser default, if this is the root container.
Unitless
While technically a relative unit, this one behaves differently, at least in terms of line-height

Leading

The other thing we need to understand is leading, and how it's calculated for CSS.

Leading (pronounced like the metal, and not the action of leadership) is the white-space above and below the text. Historically, on printing presses, this was created using thin strips of lead (thus the pronunciation) placed between the rows of letters.

This text has a 5px leading (white)

To calculate the leading, we subtract the size of the font from the line-height, and divide the remainder in half (divide the space over the top and bottom of the text). 

leading = (line-height - font-size) / 2

Example: Calculating Leading with a Relative Unit line-height

When using a relative unit for line-height, the line-height is first calculated to an absolute unit using the calculated font-size of the element where the line-height is specified. This line-height is then inherited and used to calculate the leading for child nodes that don't explicitly define their own line-height.

Assume a base font-size of 24px.

Now you have a paragraph with its font-size set to 1em and a line-height of 1.5em. Within that paragraph is a span whose font-size is set to .5em;

The line-height is then calculated using the calculated font-size (24px * 1em = 24px) of the paragraph: 24px * 1.5em = 36px.

This gives a leading of (36px - 24px)/2 = 6px. So 6px above and below the text.

This calculated line-height is what is then passed on to the children. So though the font-size remains relative to the parent, the line-height does not change, and we get a calculated font size of 24px * .5em = 12px. But a line-height of 36px. Which means, using the smaller font-size, we will wind up with a larger leading.

(36px - 12px)/2 = 12px above and below the text.

Example: Calculating Leading with a Unitless line-height

When using unitless line-height, the line-height is recalculated for every element using its calculated font-size.

Let's again assume a base font-size of 24px.

Now you have a paragraph with its font-size set to 1em, with a line-height of 1.5. Within that paragraph is a span whose font-size is set to .5em;

The line-height is then calculated using the calculated font-size (24px * 1em = 24px) of the paragraph: 24px * 1.5 = 36px.

This gives a leading of (36px - 24px)/2 = 6px. So 6px above and below the text.

This time, the line-height of the span is recalculated using its calculated font-size: 24px * .5em = 12px.

So the line-height is now calculated using this font-size to give us 12px * 1.5 = 18px;

And our leading calculation now gives us a very different value: (18px - 12px)/2 = 3px above and below the text.

Demonstration

Since you can't inspect leading in any dev tools that I'm aware of, I put together a codepen to demonstrate the calculated leading for values that at first glance seem like they should be equivalent using borders.

You can see how you can quickly end up with strange problems if you don't use unitless line-height.

See the Pen Extra spacing between lines by Thomas Pietrosanti (@Rykus0) on CodePen.

Of course, we don't always use unitless line-height. There are situations where you want to specify a specific line-height, such as vertically centering text with an icon. But for the most part, if you're inheriting a line-height, you should drop the unit.

Labels:

Comments

Post a Comment

Popular posts from this blog

SASS Converts Zero Opacity 'rgba' To 'transparent'

I recently had a strange problem after updating SASS. I have a modal dialog with a semi-transparent overlay behind it. For modern browsers, I'm using a CSS transition from rgba(0,0,0,0) to rgba(0,0,0,.5) For older browsers (namely IE8), I'm using some JavaScript to apply the transparency and animate the transition. To make sure the background gets set correctly, I'm using the standard fallback strategy of defining the background as background: rgb(0,0,0); right before the rgba line. This worked fine, until SASS optimized my code by changing background: rgba(0,0,0,0); to background: transparent; The reason? It's 2 characters shorter. Yes, we've now saved 2 bytes of easily compressible text in exchange for breaking my code. Why did it break? Well, if you haven't already figured it out, normally a browser that doesn't support rgba will simply skip that property and move on. But transparent is supported. So now, instead of h...
Post a Comment
Read more

Flags vs Vendor Prefixes for Experimental CSS

Google recently announced that it will be switching Chrome's rendering engine to a fork of Webkit, called “Blink”. If you're interested, you can read their blog post about Blink . One of the changes we will be seeing in Blink, is the use of browser flags in place of vendor prefixes . What this means, is that rather than prefixing experimental CSS with -webkit-, -moz-, -ms-, -o-, -khtml-, etc.; We will be required to enable these attributes using a flag in the browser (like the ones currently at chrome://flags). If you ask me, both ways have their advantages and disadvantages. Though, in the end, I lean towards the flags over the vendor prefixes, and here's why: #1 Code Bloat On average, using CSS with vendor prefixes requires writing it 5 times . Every time you use it . #2 Future Friendly Eventually, prefixed code will be replaced by the unprefixed code. #3 Browser Dev Friendly Browsers tend to continue to support the prefixed code, even if it doesn...
Post a Comment
Read more

Automatically Calculating Foreground Color using SASS

I ran into the problem, as I'm sure many others have, where I wanted to dynamically assign background colors to my components, but also needed to adjust the foreground color to be readable and visually appealing. It's easy for something to fall through the cracks when changing colors, and then we end up with unreadable text. So to try and avoid this, I put together a SASS function that selects a color for text based on the background color you give it. This also performs checks to make sure the contrast meets a given Accessibility spec (as per W3C rules). So far I've had pretty good results with it. Please feel free to tinker and use this in your own projects. It's far from perfect, but it has See the Pen Calculate Foreground Color by Thomas Pietrosanti ( @Rykus0 ) on CodePen .
Post a Comment
Read more