Gutenberg: Classic block removing paragraph end tag on save

[kfts]

Describe the bug
The end paragraph tag is missing in the post contents sent to the rest API save call from the classic block if that paragraph contains a line break and the starting p tag has an attribute.

To Reproduce
Steps to reproduce the behavior:

1. Create new post in Gutenberg
2. Add Classic Block and switch to Edit as HTML
3. Add
   <p class="classy">Here
   is a paragraph</p>
4. Publish Post
5. See Request Payload in debugger or look at post in database. content property is:

"<p class="classy">Here↵is a paragraph"

Expected behavior
end tags to remain

Screenshots

Desktop:

• OS: Windows 10 64 bit
• Browser Chrome
• Version 70.0.3538.67

Additional context

• Replicated on both Gutenberg plugin 4.4.0 running on WordPress 4.9.8 and WordPress 5.0 beta 3

[kfts]

Sorry, that's Gutenberg plugin version 4.2.0

[designsimply]

Tested and confirmed by checking the post content in phpMyAdmin after entering the following HTML in "Edit as HTML" mode in a classic block:

<p class="classy">This
is my paragraph with a line break in it.</p>

^{Tested with WordPress 4.9.8 and Gutenberg 4.3 using Firefox 63.0.1 on macOS 10.13.6.}

@kfts I checked the database directly in my case, but could you tell me exactly how to get to the same Request Payload from your screenshot? I would like to learn that. 🙂 It looks like the Network panel in Chrome's web developer tools to me, but I wasn't sure what to filter for or when to check that (would it be right after saving in the editor itself?).

[kfts]

@designsimply You're correct, it's the Network panel in Chrome's DevTools. When you click Update with it open, you'll see a rest API call to /index.php/wp-json/wp/v2/posts. Click on it, select Headers and you can expand the "Request Payload" to see what is being sent over.

[designsimply]

Cool. Spotted it! (screenshot) Thanks for the tip. 😁

[youknowriad]

I was not able to reproduce the issue. I think it's probably fixed.