Margin appears around header when I add post content (works fine on pages)

I have a header that extends to the edges of the screen. Works fine on Page templates, even with content in it,

but when I duplicate the page template and try to add post content, a white margin appears around the header.

Any idea what is causing that and how I can fix it?

Does it also do this on the real webpage outside of the builder?

Sometimes the builder has some caching issue. Not sure if it is builder or browser cache. If it works fine outside the builder you can just ignore it. There’s this reload button inside the builder (top center) that might fix it.

Clearing browser cache inside google chrome is opening inspect tool, rechtclick on reload page, earase cache and force reload).

It is the same outside the builder.

I’ve even tried duplicating the template, changing the post content, rebuilding the template from scratch.

There is something about post content that changes the margins and I don’t undesrtand how that can happen, considering it’s like a ‘child’ of the page template

Thats odd as it even extents beyond the header. Like some global setting is added or so.

Do you happen to have some custom css addressing section margin?

There’s no global margin option so i have no idee where to look..

Can you try the inspect tool to see if you can find the origin of the margin?

That’s a little above my skill level. This is what I see when I inspect the white margin but I don’t know what to learn from it.

Can you share the url?

If you choose inspect again on the margin part it should open the inspect code at the place where you click to inspect (take the top margin). It will then show all settings related to how it is made

Sure, it’s here. Thank you.

There seems to be 20px pading added by product pricecalculator script on line 116

is this an external script? Maybe try to put the conflicting item inside another container to restrain it

1 Like

Ah yes!
Ok. Wonderful. Thank you. I think I can fix that.
So kind of you thank you.

That fixed it. Thank you @Ferry :raising_hands: