Indesired elements with TinyMCE 5.0.3
See original GitHub issueExcerpt contains single <br>
even if left empty in manager
StandardPage.SinglePage<StandardPage>.Data.Excerpt
StandardPost.SinglePost<StandardPost>.Data.Excerpt
This way it cannot simply be checked with string.IsNullOrEmpty
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
TinyMCE 5.0.3 | Docs
Updates and enhancements ... The new TinyMCE 5.0.3 editor comes with significant changes to the previous versions. Improved solutions have been ...
Read more >Noneditable plugin | Docs
This plugin enables you to prevent users from being able to edit content within elements assigned the mceNonEditable class.
Read more >List of upcoming changes for TinyMCE 6 | Docs
This page lists the upcoming changes planned and announced for TinyMCE 6.0, including features that are deprecated and marked for removal.
Read more >Migrating from TinyMCE 5 to TinyMCE 6
The process for setting up a basic TinyMCE 6 instance is the same as TinyMCE 5. Most configuration changes in TinyMCE 6.0 only...
Read more >Checklist plugin | Docs
The Checklist plugin helps the user keep track of all required actions by creating a simple, clean, and easy to use TODO list....
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 FreeTop 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
Top GitHub Comments
@tidyui I have tried it and it seems to solve the problem.
@filipjansson Yes I see that the two blocks retrieve their data differently, this is probably the case with the excerpt as well as this is probably based off the
html-block
component. We should try to just replacee.target.innerHTML
withtinyMCE.activeEditor.getContent()
and see if it solves the problem.