Skip to content
New issue

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

Classic block still displaying unwanted p and br tags when Edit as HTML is chosen #10837

Open
bobbingwide opened this issue Oct 20, 2018 · 5 comments
Labels
[Block] Classic Affects the Classic Editor Block [Type] Bug An existing feature does not function as intended

Comments

@bobbingwide
Copy link
Contributor

Describe the bug
Classic block still displaying unwanted p and br tags when Edit as HTML is chosen. These are somewhat misleading. These unwanted/added tags are not saved in the post_content during update.

To Reproduce
Steps to reproduce the behavior:

  1. Using the Classic editor create a post something like this.
Classic block still displaying unwanted p and br tags when Edit as HTML is chosen. These are somewhat misleading. These unwanted/added tags are not saved in the post_content during update.
<!--more-->

[clear]

[bw_csv]A,B,C
1,2,3
4,5,6
[/bw_csv]

end of post
  1. Edit using Gutenberg and see the contents in the Classic block
  2. Choose More Options > Edit as HTML
  3. Notice p and br tags being added.
  4. Edit the text and perform an Update.
  5. View the post.
  6. The unwanted tags have magically disappeared. The content is actually how I want it.

Expected behavior
The Edit as HTML display should not be showing the p and br tags. It's misleading.

Screenshots
If applicable, add screenshots to help explain your problem.

The first screen shot is step 4.
image

The second screen shot is step 7. You can see that I'd edited the content.
In the sidebar you can see the raw post_content that has been saved as wanted.

image

Desktop (please complete the following information):

  • OS: [e.g. iOS] Windows 10
  • Browser [e.g. chrome, safari] Chrome
  • Version [e.g. 22] Version 69.0.3497.100 (Official Build) (64-bit)

Additional context

@designsimply designsimply added the Needs Testing Needs further testing to be confirmed. label Oct 23, 2018
@ellatrix ellatrix added [Block] Classic Affects the Classic Editor Block and removed [Block] Classic Affects the Classic Editor Block labels Oct 31, 2018
@tisayama
Copy link

tisayama commented Nov 1, 2018

I have the same problem. Does anyone have an update?

@danicholls
Copy link

Is this still a problem?

@bobbingwide
Copy link
Contributor Author

bobbingwide commented Mar 26, 2019

Yes.
36B60B4C-3E0E-4A37-A8CD-AF7882DA1C68

7D5325CC-90A9-4437-90EF-6616D1501E70

@youknowriad youknowriad added [Type] Bug An existing feature does not function as intended and removed Needs Testing Needs further testing to be confirmed. labels Aug 22, 2019
@paaljoachim
Copy link
Contributor

Hey @bobbingwide Herb
Can you retest with the newest version of WordPress and Gutenberg?
Thanks!

@bobbingwide
Copy link
Contributor Author

Yes. Same result if I follow my original instructions.

<p>Classic block still displaying unwanted p and br tags when Edit as HTML is chosen. These are somewhat misleading. These unwanted/added tags are not saved in the post_content during update.<br /><!--more--></p>
<p>[clear]</p>
<p>[bw_csv]A,B,C<br />1,2,3<br />4,5,6<br />[/bw_csv]</p>
<p>end of post</p>
<p>perform update.</p>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Classic Affects the Classic Editor Block [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

7 participants