Hi!
It’s been a long time since my last report was made.
Today, I am going to share something about the custom tag of a container. While I’m recently updating my site to 1.3.7 from 1.3.3, I noticed that there is something Bricks can do better.
Currently, when I add a heading element, the heading tag will be wrapped by a div.
*the title-line is the global class I created to do something I want.
So, to prevent this extra div, I had to use a basic text element(I typed container in the screenshot) and choose h4 for the custom tag. So I get the clean h4 tag HTML output as below.
Then I noticed that the heading didn’t reflect the preset style I have styled for the h4 heading in the backend. So, I can’t visualise it in the backend when I edit the page. It’s working in the front end.
Thanks so much for reaching out again!
If you add the styles for your headings within your Theme Styles, they will apply to both bricks headings and, for example Gutenberg headings or your “custom” basic text headings that don’t have the .bricks-heading class attached.
Well, that doesn’t just apply to the heading element. We already have an idea on the Idea Board. Reducing the number of DOM elements makes many things much more accessible. In addition, it reduces sources of error (for example, styles that are applied to the wrapper but should apply to the element itself).
I am firmly convinced that this step will change a lot but requires a complete overhaul of each element and the builder. But we take this very seriously and implement it sooner rather than later.
