Confusing creation of containers in Elementor v4
-
Hi, I was looking forward to testing v4 on the new project, but instantly stumbled upon some issues. So, I’ve started building the header and the first container is a simple block with a blue background and the email address in it, it should be “boxed”, meaning the width should be contained in 1280px.
So, first of all, I discovered that for new v4 elements I can’t define the “container” class, and, since I have a blue background and I need padding of 20px around the container for mobile devices, I need to have another div block in place for that. So, right from the start the editing experience is more complicated than v3, because in v3 I just use a “Container” widget, which has a “boxed” or “full-width” options built in and I can define padding in it easily, so even the structure inside the editor looks cleaner:
https://cleanshot.com/share/lPGzgTtZ
Okay, so I’ve created a custom class “.containr” for v4 Div block where I’ve defined a custom width of 1280px, and I’ve set the margins to “auto” so it is centered. It’s reflected correctly on the editor screen:
https://cleanshot.com/share/skhWLRrz
However, when visiting the live page, v4 and v3 blocks look different:
https://cleanshot.com/share/9ynzgyzB
Look at my settings in the Elementor editor (for a custom v4 container):
https://cleanshot.com/share/ChYW0pPR
None of these settings are applied to the actual rendered container on the live page (padding should be 0, margin should be auto and max-width should be defined):
https://cleanshot.com/share/FJSdpFVr
So, not only is the process of creating a basic container is much more complicated, involves two different div blocks and much more steps, it’s not even working properly – I see different styles in editor and on front-end. And the cherry on top is that you declare v4 less bloated than v3, but if we directly compare the DOM output for my v4 and v3 solutions, you will see they are almost identical:
https://cleanshot.com/share/4b0zLCsm
So, what is the point of all of these “improvements” if there’s literally zero performance benefit, more friction and time spent; and it’s generally bugged?
You must be logged in to reply to this topic.