Make WordPress Core

Opened 4 years ago

Last modified 5 months ago

#48730 new defect (bug)

Twenty Twenty: Wide and Full Width blocks top and bottoms margins don't respect original design causing layout issues

Reported by: collet's profile collet Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.3
Component: Bundled Theme Keywords: needs-testing
Focuses: css Cc:


In the original design:

  • wide width blocks had vertical margins of 4rem on small devices, 6rem for @media (min-width: 700px) and 8rem for @media (min-width: 1000px)
  • full width blocks had vertical margins of 5rem on small devices, 6rem for @media (min-width: 700px), 8rem for @media (min-width: 1000px) and 10rem for @media (min-width: 1220px)


  • wide width blocks have vertical margins of 4rem on all screen sizes
  • full width blocks have vertical margins of 5rem on all screen sizes except 10rem for @media (min-width: 1220px)

The correct values don't appear because there is an error in the CSS declarations at the lines below. While they intend to set the margins, they do nothing as complex selectors can't be set in the :not() pseudo-class (

.entry-content > .alignwide:not(.wp-block-group.has-background),
.entry-content > .alignfull:not(.wp-block-group.has-background) {
    margin-bottom: 6rem;
    margin-top: 6rem;

.entry-content > .alignwide:not(.wp-block-group.has-background),
.entry-content > .alignfull:not(.wp-block-group.has-background) {
    margin-bottom: 8rem;
    margin-top: 8rem;

it's important to set these margins back to their original values because currently 2 consecutive wide columns blocks don't display properly (because the negative margin-top calculation for the second columns block was based on the original margin values

Change History (3)

#1 @ianbelanger
4 years ago

  • Keywords needs-testing added

#3 @poena
5 months ago

Would it be reasonable to remove the theme styles for these block margins and rely on the defaults provided by core?
The core styles have also changed several times since this issue was opened, and there are likely other conflicts that needs to be tested.

Note: See TracTickets for help on using tickets.