Make WordPress Core

Opened 7 weeks ago

Closed 7 weeks ago

Last modified 7 weeks ago

#61731 closed defect (bug) (duplicate)

Body element specificity still bumped

Reported by: cabrailsford's profile cabrailsford Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.6
Component: Editor Keywords:
Focuses: css Cc:

Description

After upgrading to 6.6.1 today, I noticed that the body element is still being wrapped as :root :where(body) for output. Is the body element not considered a top-level element-only selector?

For my instance, I have left/right padding in my theme.json to output in the editor, but am overriding that on my frontend with just the body selector to remove the padding. However, 6.6's specificity supersedes that, and so now I need to increase specificity to compensate.

If there's a reason the body element was left out of the change, I understand, but I wanted to mention it in case it was missed in the update.

Change History (4)

#1 @hellofromTonya
7 weeks ago

  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Hello @cabrailsford,

Welcome to WordPress Core Trac.

This particular bug fix was not included in 6.6.1, but instead is being tracked in #61704 and is planned for 6.6.2.

I'm closing this ticket as a duplicate of #61704, i.e. to keep the discussion and resolution in one Trac ticket.

#2 @hellofromTonya
7 weeks ago

  • Version changed from 6.6.1 to 6.6

#3 @cabrailsford
7 weeks ago

Thanks @hellofromTonya! As this was my first report, it looks like I missed that other open ticket. Appreciate that you all are tackling it, and that it will be coming sooner than later.

#4 @hellofromTonya
7 weeks ago

No worries @cabrailsford. Thanks for reporting it.

Are you available for testing?

If yes, please consider testing the patch (bugfix) in #61704 and then leaving your findings in the ticket as either a Test Report or comment.

Note: See TracTickets for help on using tickets.