WordPress.org
Get WordPress

Make WordPress Core

Opened 5 years ago

Closed 14 months ago

#52771 closed defect (bug) (duplicate)

5.7 issue p tag added to html comment

Reported by: fjcontrib Owned by:
Priority: normal Milestone:
Component: Editor Version: 5.7
Severity: critical Keywords: reporter-feedback close
Cc: Focuses:

Description

5.7 issue p tag added to html comment in editor (classic) this creates leaded gaps in display therefore throwing out design layouts. Have downgraded to 5.6.2 until solution confirmed. Thank you for the good work. Fred

Change History (8)

#2 @SergeyBiryukov
5 years ago

  • Milestone Awaiting Review → 5.7.1

Hi there, welcome to WordPress Trac!

Thanks for the report, moving to 5.7.1 for investigation.

This ticket was mentioned in ​Slack in #forums by vladytimy. ​View the logs.
5 years ago

This ticket was mentioned in ​Slack in #forums by alanfuller. ​View the logs.
5 years ago

#5 @SergeyBiryukov
5 years ago

  • Keywords needs-patch removed
  • Milestone 5.7.1
  • Resolution → duplicate
  • Status new → closed

This appears to be the same issue as in #52764, which has a bit more information. Let's continue the discussion there.

#6 @fjcontrib
5 years ago

  • Resolution duplicate
  • Status closed → reopened

No - my ticket is just about p tags being added to html comments <--. The other thread is of no use to me.

#7 @SergeyBiryukov
5 years ago

  • Keywords reporter-feedback added

Just noting that while the initial #52764 description is about media embeds, the issue is not limited to that, and can happen with any <p></p> tags that were not previously visible on the page, but are visible now.

As noted in comment:6:ticket:52764, this is due to the change to block library paragraph styles in ​PR 27995.

If you add this to Appearance → Customize → Additional CSS as a workaround, as suggested in comment:12:ticket:52764, does that fix the issue for you?

body p:empty:before {
	content: none;
}
Version 0, edited 5 years ago by SergeyBiryukov (next)

#8 @karmatosed
14 months ago

  • Keywords close added
  • Resolution → duplicate
  • Status reopened → closed

Duplicate of #52764.

This does look to be the same issue as the linked one. For now, I am going to move this to close to reflect that with at status of duplicate. However, if more information can be given to counter this we can always reopen again. Thank you everyone for collaboration on this.

Note: See TracTickets for help on using tickets.