We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At the moment, an attribute element that is in otherwise empty container element receives bogus BR:
<p> <strong><br /></strong> </p>
However it causes a problem when there is also a UI element in that container:
<p> <strong><br /></strong> <span class="myUi"></span> </p>
Because the UI element is rendered incorrectly.
We should force rendering such attribute element after all UI elements. The attribute element should be pushed if its parent has no non-UI elements.
The text was updated successfully, but these errors were encountered:
What's your plan for this? We also have https://github.com/ckeditor/ckeditor5-engine/issues/1071 so if that can be fixed "by the way", it'd be lovely :D
Sorry, something went wrong.
My plan for this is to make it quick. #4142 may need a bigger refactor and better planning.
Merge pull request #1073 from ckeditor/t/1072
43b6ea9
Fix: AttributeElement with bogus <br /> will now be placed after all UI elements which will fix how those elements are rendered. Closes #1072.
scofalik
Successfully merging a pull request may close this issue.
At the moment, an attribute element that is in otherwise empty container element receives bogus BR:
However it causes a problem when there is also a UI element in that container:
Because the UI element is rendered incorrectly.
We should force rendering such attribute element after all UI elements. The attribute element should be pushed if its parent has no non-UI elements.
The text was updated successfully, but these errors were encountered: