Thanks for your thoughtful response and sorry for my delayed reaction.
Imagine you want to create an advanced layout using flexbox (using custom CSS) but at the same time you want to take advantage of the PRO builder V2 elements –in the content area (not in the header)– then in many cases you will need an extra HTML element to function as a wrapper so the flexbox layout can work –because sometimes the structure section>>row>>columns>>elements is not enough for elaborated flexbox layouts–. Using the text and raw elements would prevent us from taking advantage of the V2 elements. In a few words, having a wrapper element in which to nest V2 elements would allow us to combine the power of advanced layouts with the convenience of the V2 elements (much more tuneable than shortcodes).
And you can always add a shortcode within your HTML code, like
<aside>[cs_button]</aside> and will function the same but will not work on v2 elements. Or do you mean creating a wrapper for each HTML element? With so many HTML elements, it would slow down the builder or system.
This in fact could be a different feature request –though aplicable to the wrapper element–. What I propose is to give us the ability to choose the html element for the (Pro builder) rows and columns, so that we could use a different structural semantic HTML element (
<header> (that can be used within sections as well as for the main header of the page), etc.) instead of the current default
<div> (that forms the row or the column). This could be a simple dropdown.