Ahmad Shadeed blogs the sentiment that we might not need to lean on position: absolute
as much as we might have in the past. For one thing: stacking elements. For example, if you have a stack of elements that should all go on top of each other…
.stack {
display: grid;
}
.stack > * {
grid-area: 1 / -1;
}
All the elements occupy the same grid cell at that point, but you can still use alignment and justification to move stuff around and get it looking and behaving how you want.
What you are really saying with position: absolute
is I want this element to be entirely removed from the flow
such that it doesn’t affect other elements and other elements don’t affect it. Sometimes you do, but arguably less often than your existing CSS muscle memory would have you believe.
I’ll snag one of Ahmad’s idea here:
Both the tag and the title are positioned in a way we might automatically think of using absolute positioning. But again, something like CSS Grid has all of the alignment features we need to not only stack them vertically, but place them right where we want.
This is nice but I would argue that using position:absolute and left, top is far more readable and probably a fair bit more intuitive.
Agreed, it would be much more readable
I think the most important thing is the Web layout remains cross browser compatible and renders quickly and nicely on all devices irrespective of screen constraints.
This is nice but i think using absolute or relative positioning is much more understand and direct.