Basic text outputs as <div>text</div> on frontend. Desired output is <p>text</p> as we normally would do in VS Code or any other code editor.
Same with rich text except it does add the p tag but again inside a div like this <div><p>text</p></div> why the unnecessary div?
Advanced Themer says hi.
Alternatively, you should be able to overwrite the built-in Basic Text element with modified output to replace the default <div> tags with p tags.
Hi Soum,
Thanks so much for your report!
The default tag for the basic text is <div>, but you can change it depending on the input. If you are using plain text, set it to <p> (or any other tag that fits). If you are using a dynamic data tag that already contains WYSIWYG styles (aka tags), leave it as a div.
The rich text element is a WYSIWYG editor, so it adds tags automatically.
Changing it to p tag is adding a 48 px bottom margin, gets removed as soon as I change the p tag back to div tag
Check this out. It’s happening to everyone. This is not normal behaviour and should not exist. Makes no sense to add 1.2 em margin when changed to p tags.
Why compare the behavior of vscode and bricks? These are different applications for different tasks. That’s why they behave differently. Each widget and html tags have basic styles to make it easier for users to create content. If you don’t like the basic styles, you can always change them to your own, but do not require this from the developers. the solution to your problem in one line of code that needs to be inserted into custom css…
:where(p) { margin: 0em; }
