For users that use position relative to position the elements with an absolute position this can break all my sites once I update!!
Why you didn’t do it in a progressive way so old elements don’t break??
1 Like
See the note in the changelog…
"If you are experiencing layout offsets due to the removal of the position: relative, you can restore this style by adding the following line of code to the style.css file of your Bricks child theme (or via the “Custom CSS” Bricks setting):
[class*=brxe-] { position: relative; }
"
This will add it back in.
4 Likes
Yes indeed. That can put things back to how they were.
HOWEVER… This isn’t a “bug”, it’s a bold and proper step forward and needs to be done (and now is better than months or years later).
It’s a CSS best practice for all elements to be ‘static’ by default. Yes, it will break sites created with previous versions, but the code you mentioned should fix it for those people (I won’t be using it though, I’d rather fix the issues on the site).
2 Likes
Yes, I agree. Fix it now or suffer later especially when there are more sites built.
2 Likes
Just to clarify, I meant adding that CSS temporarily for the update if the user hasn’t yet had chance to fix any layout issues on live sites that are updated (when the stable version is released).
in the long run, obv it’s better to apply the relative manually where and when it’s needed.
2 Likes
Got it. Good followup. 
You are right, I hadn’t seen it.