Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Page break block breaks styling on all pages except the first #89719

Closed
dolgelukkig opened this issue Apr 21, 2024 · 1 comment
Closed

Page break block breaks styling on all pages except the first #89719

dolgelukkig opened this issue Apr 21, 2024 · 1 comment
Labels
[Feature] Core Blocks Blocks that come with Gutenberg. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. Needs triage Ticket needs to be triaged [Platform] Simple [Pri] Low [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug

Comments

@dolgelukkig
Copy link

dolgelukkig commented Apr 21, 2024

Quick summary

When using the page break block the user found that the width limit of the column blocks they added to all the blocks was only applied on the blocks that were displayed on the first page. Blocks displayed after the page break do not use full width and are not stacked correctly even though the same styling was added to those blocks in the editor.

Steps to reproduce

Create a page
Add content inside the columns block, in this case: 2 columns, image on the left, Title + text + link in the right column.
Add page break between the different columns
The width and the stacking of the columns was only displayed correctly on the blocks that displayed before the page break.

What you expected to happen

I'd expect the content after the page break to use the same width and stacking as the blocks before the page break.

Blocks before the page break:
Markup on 2024-04-21 at 10:55:40

Blocks after the page break:
Markup on 2024-04-21 at 10:56:04

What actually happened

The columns width and stacking is not applied on blocks after the page break.

Impact

One

Available workarounds?

Yes, easy to implement

Platform (Simple and/or Atomic)

Simple

Logs or notes

Tested it on my test site with Twenty Twenty-Four and I can replicate the exact issue.

Suggested the user to use the Query loop block with page breaks instead of custom blocks and page breaks.

@dolgelukkig dolgelukkig added [Type] Bug Needs triage Ticket needs to be triaged [Product] WordPress.com All features accessible on and related to WordPress.com. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Feature] Core Blocks Blocks that come with Gutenberg. labels Apr 21, 2024
@rickmgithub
Copy link

📌 REPRODUCTION RESULTS

  • Tested on Simple as per the original instructions

📌 ACTIONS

  • Closed as could not replicate (please reopen if the issue reoccurs)

Thanks so much for the report. I couldn't replicate the issue with the same set up. Are you still able to produce this on a number of sites? Feel free to reopen if you can still replicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Core Blocks Blocks that come with Gutenberg. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. Needs triage Ticket needs to be triaged [Platform] Simple [Pri] Low [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug
Development

No branches or pull requests

2 participants