In Elementor v3, we only needed a regular Container element. From its dropdown menu, we could simply select either Full Width or Box. When using Box mode and setting a background color for the container, the background would stretch full-width across the screen, while all inner content would automatically follow the Content Width defined in Elementor Site Settings > Layout (I have mine set to 1440px). This kept the content constrained to a maximum width of 1440px with a full-width background — it worked perfectly.
Now in Elementor v4, newly created containers use Flexbox by default, and this brings two major problems:
The default width is set to Full Width, which stretches all content across the entire viewport.
If I apply a background color to a Flexbox container and want the inner content limited to 1440px instead of full width, this cannot be achieved with a single container.
I already posted this feedback on GitHub. The official reply suggested nesting an inner Flexbox inside the parent one: set the outer Flexbox to full-width for the full-screen background color, then manually set the width of the inner Flexbox to 1440px to constrain the content.
The root cause is that the new Flexbox container no longer has the old Full Width / Box content width options available in v3 Containers. If you assign a fixed width directly to a Flexbox, its background color will also be confined to that fixed width, rather than extending across the full screen.
This creates an awkward workflow. Previously, we could achieve a full-width background (color or image) with content limited to 1440px using just one single container. Now we have to nest one Flexbox inside another, which results in unnecessary redundant elements.
The problem gets even worse for layouts with multiple columns. For example, if I need four child containers whose total content width must stay within 1440px, I now have to use a structure like: outer Flexbox → nested middle Flexbox → four child Flexboxes. This creates a three-level nesting hierarchy, which feels overly bloated and redundant.
This reply was modified 3 weeks ago by losvincent.
@qtwrk Thank you. Will this result in completely disabling the delay for Elementor, thereby affecting the speed to a certain extent? Additionally, I have consulted Elementor Pro’s customer support, and they stated that this is an issue with the third-party plugin and advised me to contact the plugin developer.
By the way, could you add automatic exclusion support for Elementor’s Nav Menu in future versions? For the JS delay feature of WP Rocket installed on my other websites, it automatically excludes the Nav Menu, so the issue of it not displaying never occurs.
This reply was modified 6 months, 3 weeks ago by losvincent.
@dcsupport hello,wp rocket is re-disable now,and could you share me a email,and i’ll send my site account to you directly,you can login in background and test
I apologize, but my form submissions are being intercepted as spam. I’m worried that customers may also be blocked, so I’ve temporarily paused the WP Armour plugin.
