In my ongoing experiments with both a realignment of meyerweb’s design and CSS Grid, I came up with an interesting heading-and-subheading technique I’d like to share. It allows two elements to be centered as a block, while letting them text-align with respect to each other, while still line-wrapping if necessary.
Here’s a little demobox.
Each heading-subheading pair is composed of two heading elements wrapped in another element. The wrapping element is the grid container for the headings, each of which become grid items. This is the markup I used:
<h2>These Are Grid Headings</h2>
<h3>A useful technique</h3>
If you resize your browser window, or select the “Narrow” option, you should see that the boxes surrounding the headings stays as wide as the wider of the two headings. It “shrink-wraps” them, visually speaking. In addition, those boxes stay centered within the grid container.
Furthermore, given the demo’s defaults, the two headings are left-aligned with respect to each other. You can change this: for example, if you choose to “Center-align headings”, the
h2s will center when they’re shorter than the subheadings (the
h3s). On the other hand, if you select “Right-align subheads”, then the subheads will right-align themselves with respect to the headings whenever the subhead is shorter in length.
That was actually a bit misleading: if the headings are centered, they’re centered whether or not they’re shorter than the subhead. It’s just that, if they’re longer, you can’t see that they’re centered, because left-, center-, and right-aligning them has the same effect. Ditto for right-aligning the subheads: if they’re longer, they sit in the same place regardless of their text alignment.
The alignments hold even when line-wrapping kicks in. Try narrowing things down to the point that the text starts wrapping. If you’re having trouble visualizing the two elements, turn on “Separate backgrounds” to given the heads and subheads visually distinct background colors.
So: a centered box as wide as the longest of the two elements, inside which they can align themselves with respect to each other. Here’s the CSS that makes this possible:
That’s pretty much it. The first and third grid tracks are set to be a minimum of
1em, and a maximum of
1fr. Given the second track (which I’ll get to in a moment), this means the two tracks will split any free space within the grid container, down to a minimum of 1em. That’s how the centering of the box work; or, if you turn off “Boxes”, how the unbounded text sticks together in the center of the layout area.
That second track,
minmax(min-content,max-content), is what makes all the unusual aspects of this possible. What that says is: “make this grid track no narrower than the narrowest of the grid items in the track, and no wider than the widest grid item”. In practice, it’ll most likely be as wide as its widest element.
But if I just said
max-content (without having the
min-content parts) for that track width, the track would always be as wide as the widest element at its widest possible layout, which in this case means without line-wrapping the contents. That would force particularly long headings to run outside of the track, and possibly out of the grid container altogether. You can see this by enabling “Remove minmax” and narrowing things until text lines should wrap.
minmax(min-content,max-content) that avoids this fate, because that means that while the grid track (the column the head and subhead share) can’t get any wider than the widest element it contains, it’s allowed to get narrower. Thus, if the grid container gets too narrow to fit all the grid items’ maximum widths, the contents of the grid items are able to line-wrap, thus avoiding overspill. In fact, the grid items can keep getting more narrow until they reach
min-content, which is to say, the narrowest the track can get without having content of any grid item stick out of the track. Then it will stop shrinking.
And finally, if you want to see how the options you’ve selected will look in a Gridless browser, select “Remove grids” and see what happens. Some combinations may not be palatable without Grid, but remember: you can always use
@supports(display: grid) to quarantine any styles that are particularly egregious in older UAs.
So there you have it. While I’m not certain the Grid drop quotes I wrote about last month will be used in the final version of my styles — I’m still looking to see if they’ll fit with more than 17 years of vaguely ad-hoc markup patterns — it’s pretty close to certain I will use these headings, minus the boxes. I think they’re a neat effect for blog post titles and dates.
Addendum: As of May 2017, WebKit browsers (e.g. Safari) require vendor prefixes for the