#54944 closed defect (bug) (fixed)
By applying a background color to a group block, it aligns to the left in the editor
| Reported by: | eddystile | Owned by: | audrasjb |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.9.1 |
| Component: | Bundled Theme | Version: | 5.9 |
| Severity: | normal | Keywords: | has-screenshots has-patch fixed-major |
| Cc: | Focuses: | css |
Description
With Twenty Twenty Two theme, in a post edition, when applying a color background to a group block, this block align to left in the editor. It's ok in front.
Attachments (3)
Change History (18)
#1
@
5 years ago
- Component General → Bundled Theme
- Keywords has-screenshots added
- Milestone Awaiting Review → 5.9.1
- Owner set to
- Status new → reviewing
#2
@
5 years ago
Just a quick note here as I haven't tested this thoroughly, but I just dealt with a customer experiencing similar issue.
I've found out the issue was coming in my case from Gutenberg plugin applying margin: 0; on the affected block (where horizontal margins of auto coming from theme were effectively overridden with this). Not sure why though. After disabling Gutenberg plugin the issue disappeared.
Hope this helps somehow if it is related.
#3
@
5 years ago
- Focuses css added
Twenty Twenty-Two has had negative side margins on group blocks with a background since PR 336
This ticket was mentioned in PR #2281 on WordPress/wordpress-develop by petaryoast.
5 years ago
#4
- Keywords has-patch added
Trac ticket: https://core.trac.wordpress.org/ticket/54944
#7
@
5 years ago
- Keywords fixed-major added
- Resolution fixed
- Status closed → reopened
Reopening for 5.9 backport.
5 years ago
#8
Committed in https://core.trac.wordpress.org/changeset/52679
#9
@
5 years ago
Just a heads up that the padding rule does not need to be removed in order to fix the margins issue. I opened #55103 to restore it.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Hello and thanks for the report @eddystile,
I can reproduce the issue using TT2 and WP 5.9.
We need to make sure the issue is not coming from Gutenberg side, though.
Moving for 5.9.1 consideration.