How do we move logical shorthands forward?
There are several proposals, but one major road block
We’re trying to make progress on shorthand syntax for CSS logical properties. But the path forward depends on where we hope to be a decade from now.
A few new features have landed in Susy 1.0.7, even as we work on more
integrated syntaxes for 2.0. The isolate()
and isolate-grid()
mixins
help you manage the worst effects of sub-pixel rounding, while
bleed()
helps you break items out of the box.
A few new features have landed in Susy 1.0.7, even as we work on more integrated syntaxes for 2.0.
Sub-pixel rounding has always been a problem for fluid design. Susy takes care of the most egregious layout-breaking cases, but there is no way to entirely eliminate the problem.
John Albin Wilkins has a demo of the problem, as well as a proposed solution. He hasn’t eliminated rounding errors, he just found a way to keep them from piling up. Every float is positioned relative to its container, rather than the float before it. It’s a bit of a hack, and removes content from the flow, so I don’t recommend building your entire layout on isolated floats, but it can be very useful as a spot-check when rounding errors are really causing you a headache.
(Note that rounding errors can still stack up when you use a gradient background for testing. Gradient background grids are useful, but you should never trust them as a pixel-exact guide.)
Using John’s method, you can now isolate any grid element in susy,
with the simple isolate()
mixin:
See the Pen Susy Isolation Demo: Syntax by @miriamsuzanne on CodePen.
When you put several of those together, you can see how they have been removed from the flow:
See the Pen Susy Isolation Demo: Multiple by @miriamsuzanne on CodePen.
The items can overlap, and stack in any order – almost as though they are positioned absolutely.
Isolation is most useful when you are repeating the same grid math again
and again, such as image-galleries. To help with that use-case, we’ve
added the isolate-grid()
mixin. You just tell us how wide each item
should be, and we’ll calculate the locations, applying them with
nth-child selectors.
Change the span-width, and we’ll update everything for you:
See the Pen Susy Isolation Demo: Gallery by @miriamsuzanne on CodePen.
Bleed has nothing to do with isolation, it just happened to appear in the same update. Bleed uses negative margins and equal-but-positive padding to let an element’s background “bleed” outside the area it would normally occupy.
Here’s an element bleeding 1-column outside our 6-column page layout:
See the Pen Susy1 Bleed Demo: Syntax by @miriamsuzanne on CodePen.
You’ll notice that the context syntax is a bit different here:
(1 of 9)
instead of (1,9)
. That’s the direction we’re heading with
Susy 2.0, and it’s very helpful in this case, because there’s another
argument we want to access easily. Use the second argument to list which
sides should do the bleeding (defaults to “left right”). You can also
pass arbitrary widths in the first argument:
See the Pen Susy1 Bleed Demo: Sides by @miriamsuzanne on CodePen.
This can be especially useful to bleed across $grid-padding
. Simply
bleed($grid-padding)
and you’re there.
Happy coding!
There are several proposals, but one major road block
We’re trying to make progress on shorthand syntax for CSS logical properties. But the path forward depends on where we hope to be a decade from now.
Can we get this process unstuck?
The CSS Working Group recently resolved to add a size
shorthand for setting both the width
and height
of an element. Many people asked about using it to set the ‘logical’ inline-size
and block-size
properties instead. But ‘logical shorthands’ have been stalled in the working group for years. Can we…
It’s not just a shorthand for anchor()
position-area
might be my favorite part of the CSS Anchor Positioning spec, with a ton of features packed in to make things just… work. But there’s no magic here, just a few key parts that work well.