When a post has custom HTML added via the HTML tab and is saved in the Android editor, the element auto-close and/or not show up in the post as text, if it is not properly closed. Both the iOS editor and the desktop editor seem to auto close the elements, preventing them from showing up on the page as text.
Actual Behavior
When saved on Android the elements do not appear to auto-close when rendered and then show up in the post as text.
Steps to Reproduce
While editing a post, open the HTML tab and add an element. For example <p class="reference">. Do not close the element. When you save the post, the element itself will show up in the post as a text string.
Screenshots
Markup from HTML tab in post editor on Android. Note that p element is left unclosed:
Output in post showing element as text string:
Markup from HTML tab in post editor on iOS. Note that p element is closed (automatically?):
Output in post where element is closed and, therefore not being displayed as a text string:
Expected Behavior
When a post has custom HTML added via the HTML tab and is saved in the Android editor, the element auto-close and/or not show up in the post as text, if it is not properly closed. Both the iOS editor and the desktop editor seem to auto close the elements, preventing them from showing up on the page as text.
Actual Behavior
When saved on Android the elements do not appear to auto-close when rendered and then show up in the post as text.
Steps to Reproduce
While editing a post, open the HTML tab and add an element. For example
<p class="reference">. Do not close the element. When you save the post, the element itself will show up in the post as a text string.Screenshots
Markup from HTML tab in post editor on Android. Note that
pelement is left unclosed:Output in post showing element as text string:
Markup from HTML tab in post editor on iOS. Note that
pelement is closed (automatically?):Output in post where element is closed and, therefore not being displayed as a text string: