v5.0.2 editor issues: puts in tags where it shouldn’t

  • Resolved FireMyst

    (@firemyst)


    5 years, 11 months ago

    HI everyone:

    Since installing the new editor, when in “code” view (not block view), I have this little bit of code:

    <span style="display:none;">
blah blah blah blah <a href="javascript:hideMeToDo();">click to hide me</a>
</span>
<style type="text/css">
.mainelement {
	vertical-align:top;
	text-align:center;
	display:inline-block;
	float:left;
	border-style:solid;
	border-width:thin;
	border-radius:5px;
	margin:5px;
	padding:10px;
	width:180px;
	height:250px;
}
</style>

    The new block editor, regardless of what I do, ALWAYS changes it to be:

    <span style="display:none;">
blah blah blah blah <a href="javascript:hideMeToDo();">click to hide me</a>
</span>
<style type="text/css">
.mainelement { <br />
	vertical-align:top;<br />
	text-align:center;<br />
	display:inline-block;<br />
	float:left;<br />
	border-style:solid;<br />
	border-width:thin;<br />
	border-radius:5px;<br />
	margin:5px;<br />
	padding:10px;<br />
	width:180px;<br />
	height:250px;<br />
}<br />
</style>

    which causes everything to go haywire!

    Why is it putting in <br /> tags where I clearly haven’t had them previously with the classic editor?! Is this another bug in the new editor?

Viewing 4 replies - 1 through 4 (of 4 total)

  • Yes, this issue addresses it
    https://github.com/WordPress/gutenberg/issues/12668

    Thread Starter FireMyst

    (@firemyst)

    Thank you for the solution. I don’t know if that works for me yet, but briefly reading that’s just plain annoying.

    Now all our pages have to be rewritten to include a custom code block whenever we don’t want html automatically inserted into our pages?

    Grrr… that’s another 1-star rating for the editor. :-/

    They’ll fix it, I think. But it’s not fixed yet.
    You could install the Classic Editor plugin and ignore the whole problem.

    Thread Starter FireMyst

    (@firemyst)

    I did that. Thank you for the suggestion.

    I’m hoping that if they are going to fix it, they do so before 2021.

    Out of curiosity, do you know if it has the same issue with html <pre> tags?

    • This reply was modified 5 years, 10 months ago by FireMyst. Reason: Marked thread as resolved even though there's a follow up question
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘v5.0.2 editor issues: puts in tags where it shouldn’t’ is closed to new replies.