This behavior happened in Elementor first. I attributed it to Elementor, then tried creating the same layout in Toolset Layouts. It involves strange behavior after inserting a content template containing a view into the first of two columns. Before inserting the content template + view, the columns lay out side by side as expected. After, the columns stack vertically, and the second column becomes horizontally constrained.
A: Behavior before inserting the content template + view. We're looking at the bottom half of the page. See images A-Layout.jpg and A-Screenshot-with-code.jpg. Two columns, the first occupying five grid spaces, the second taking the remaining seven, with the column divs showing up one right after the other, (one with class col-sm-6, the other with col-sm-7). No problem here, it lays out as expected.
B: After inserting the content template + view. Same layout with the addition of the content template + view (code below). See the B-series of screenshots. Here the entire second column div, with class col-sm-7, is inserted eight layers deep inside the div containing the first column. Inserting another content template without this view did not produce this behavior. You can see the page here: hidden link
Thank you for contacting us and I'll be happy to assist.
We've recently identified an issue in the bootstrap grid markup generated automatically, by the "Loop Editor" in the views.
Only when the number of columns is set to 1 (as in your view - <wpv-loop wrap="1" pad="true"> ), it results in a missing closing div tag, per loop item. This has been reported to the concerned team already and I'll update you as soon as there is some progress on it.
For now, you can manually update your view's content in the "Loop Editor" to:
Thank you Waqar. Yes, that fixes it for now. Please keep me in the loop for when this issue is resolved.
FYI, very interesting. Setting up the same layout in Oxygen, I do not get this issue at all. The content renders as expected with the original Views code. Do you have any idea why that might be?
Gald that the page's layout is fixed and I'll update you once the issue is resolved.
Since the markup of View is generated through the toolset, the issue should be reproducible with the third-party page builders like Oxygen as well (unless the layout generated through that page builder includes improperly balanced div tag(s) of its own, which balances out the difference).
A quick way to test if the page's generated source code is properly balanced or not is to use validator tool like hidden link
If you could share a link to the page, with Oxygen builder and default code in the view's loop editor, I'll be happy to look into that as well.