Forum Replies Created
-
Posts
-
Hi Ismael,
I’ve added the links to the affected pages in the private content.
We’re currently using the ‘Masonry’ builder element to display the posts.After further investigation it seems that code in the child theme is causing the trouble. This thread can be closed.
Hi Ismael,
Thank you for the clarification. I think it’s a somewhat strange choice here because not all of the actual page main content will be put in the <main> tag when using a color section. Only the content up until the very first color section on that page is put inside the <main> tag. In my opinion it would be logical to have the <main> tag always wrap the page’ content. No matter what. So the color sections as well.
The other ‘main tag’ in the header.php is just a <div> tag with an ID of ‘main’ to it. Not an actual <main> tag. Which is logical in this case since it wraps sidebars and the footer as well.
Hi Rikard,
Thank you for your reply. I’m not mixing up the main tag and the div with ID main.First code snippet
If you check the first code snippet, you will see that the main tag starts at line 23 and closes at line 28. This is only wrapping the first content section and not the other two color sections on rule 31 and rule 42: https://imgur.com/a/AIbZxLrSecond code snippet
You won’t find a main tag anywhere in the code. I would expect a main tag wrapping all the page content.Third snippet
Working as intended. main section starts at line 21 and wraps the full page content until the sidebar: https://imgur.com/a/S6EKPFEUnfortunately not, it’s on a local development environment. But if you place the progress bar in a few tabs inside a tab section and switch to mobile view, you’ll see this issue. Make sure to refresh the window first after switching to a mobile sized screen.
Here you can find a wetransfer link with a screen capture reproducing this issue:
https://cleverstrategy.wetransfer.com/downloads/16bd8b3b1944e83127bdb04f04c5b94220200828061339/7bdf7f29bb0b52f4532afe328ca021d020200828061339/fae02d
