Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Some fields insert unnecessary markup into templates
See original GitHub issueCurrent:
<div class="rich_text"><p>hello world</p></div>
Ideal:
<p>hello world</p>
Issue Analytics
- State:
- Created 8 years ago
- Reactions:15
- Comments:14 (10 by maintainers)
Top Results From Across the Web
Some fields insert unnecessary markup into templates -
Some fields insert unnecessary markup into templates.
Read more >Bare Templates: Removing Unnecessary Markup in Twig files
In this post, I'll introduce you to the concept of bare templates, and how you can remove unnecessary markup from your Twig templates....
Read more >Bare Templates: Removing Unnecessary Markup in Twig files
In this post, I'll introduce you to the concept of bare templates, and how you can remove unnecessary markup from your Twig templates....
Read more >Drag and Drop Templates - HubSpot Developers
Drag and Drop Design Manager templates are templates built using a visual builder. They are not recommended for new templates as coded ...
Read more >add field to a form if necessary django - Stack Overflow
Your form would have to be constructed based on some variables passed to it from your POST (or blindly check for attributes).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Resolved via #6036
Generally we want to keep the proliferation of settings in check – but we’ve recently added a setting for a very similar type of “Wagtail shouldn’t be opinionated about HTML” in
WAGTAILEMBEDS_RESPONSIVE_HTML, making this type of front-end customization opt-in. So – it feels like that wrapperdivcould get the same treatment. A single site-wide setting might not be granular enough for all, but it’s probably a meaningful improvement nonetheless.I’ll mark this as “Design decision needed” so we bring it up and discuss at a future core team meeting.