[Support request] Container small bug latest release?

[blackbird]

Hi I believe there is a small bug in the latest release related to container blocks.
I copied and updated a Footer-Element with the older type of containers (and more containers etc inside it) automaticly by clicking on “Use legacy layout system”. Working fine.

EDIT:
My footer element consist of a full width container “A” with a background image. The auto update works fine.
Inside container A I have a container “B” with all the content in it (text, buttons, etc). Container B is originally set to contained width (1200). The auto update works fine.
After the update to the new flex containers I do some content changes and decide to change container B to full width, (it is still inside container A). It looks alright in the backend, the content is full width.
I click publish.
But on the frontend container B is not full width.
And with the Inspektor I find there is still a settting for “1200”. And also it is not centered but squezed to the left.

And then I changed the width of the former inner container from “inner container width” (1200) to “full width”. Everything looked as it should in the backend, the width was full as I wanted.
But when I published the Element-footer, on my site, it did NOT look like it did in the backend. Instead everything was pushed to the left, instead of center and full width. (Yes I cleared chache.)

After the first panic I found that in the frontend somehow the container was still restricted to 1200 px, like the older container was. Even thou it looked wide in the backend!

I searched and found there still was a Sizing: Max width setting for container B, that had been automaticly set to sitewide 1200 px.
But then how/why did it look like a full width container in the backend? A bug?

I deleted the max width and then the container B was full width as I wanted it also in the frontend. So problem solved, but some kind of bug I guess between how it looks in the backend and frontend?

[David]

Hi there,

this:

changed the width of the former inner container from “inner container width” (1200) to “full width”.

I don’t understand.
After you converted the container by unchecking the “Use legacy layout system”. and following the steps provIded. Could you still see the old “inner container width option” ?

[blackbird]

Sorry, the new container is “just a container”. I mean it is the one that “used to be the inner container”.

[David]

Before converting was the Inner Container set to Full Width ?

[blackbird]

Hi, I updated my first text, hopefully less confusing now. (Nothing is “inner container”, I used the term wrong.)

I guess the “bug”, that the container B was both (?) changed to full width but still had a max 1200 restraint set, is was caused I also had to refresh the backend page every time I had tested “preview as a mobile”. Because after that it did not go back as it should to “desktop preview”, but it was squezed together.

[Fernando]

Hello there,

It’s a max-width.

Viewing from the backend, your view may not have been over 1200px since there are sidebars for editing.

Does switch from desktop to mobile view and back to desktop view change anything?

[Author]

Posts