How to contain a fixed positioned element

It's easy to contain absolute positioned elements. Things get a little trickier when you want to contain a fixed positioned element without changing its stylings.
Containing a fixed positioned element
It's easy to contain an absolutely positioned element without changing its stylings, so the elements top and left properties are relative to the container - all you need to do is assign a position: relative property to the container. Things get a little trickier when you want to contain a fixed-positioned element.
One case scenario when it's suitable is a situation in which you have two layouts, for example, user's and admin's, and both of them contain a fixed positioned header. From the admin panel, you would like to have a preview of the user's layout when you create a new blog post to make sure that it matches visually.
Double wrapper
One solution is to create two wrappers: one that's relatively positioned and a second that's absolute.
.wrapper {
position: relative;
}
.fixed-wrapper {
position: absolute;
}
.fixed {
position: fixed;
top: 0;
}
<div class="wrapper">
<div class="fixed-wrapper">
<div class="fixed">Hello World!</div>
</div>
</div>
The disadvantage of this method is that it requires you to set width and height in order to maintain responsiveness, and it won't work well with content having variable height.
Trick with transform
According to the spec:
For elements whose layout is governed by the CSS box model, any value other than none for the transform results in the creation of both a stacking context and a containing block. The object acts as a containing block for fixed positioned descendants.
So, if you set a transform property to the container, it becomes a containing block.
.wrapper {
transform: translateZ(0);
}
.fixed {
position: fixed;
top: 0;
}
<div class="wrapper">
<div class="fixed">Hello World!</div>
</div>
On the other side of the coin, this trick prevents child elements from behaving like fixed, even though such behaviour isn't described in the specification.
Related posts
Dive deeper into this topic with these related posts
You might also like
Discover more content from this category
Sooner or later you'll have to change the null constraint in one of your DB relations. How to do it easily in Ecto?
Sometimes you need to do some database operations at once. A simple example: User-A transfers money to User-B. Updating just one balance at the time creates a risk of data desynchronization. What if the first DB operation goes well but updating the second user’s data fails? Sounds like a hard to catch vulnerability.
Ensuring that GraphQL mutations properly update your Apollo client's cache can be a bit tricky - here's how to manually control that.
