-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Layout Grid Block Content Overlaps in Page/Post Editor When Large Image is Set to 100% #68738
Comments
This appears to be due to a few of the Image blocks in the Layout Grid on this page -- if they're set to 100% width after being added to the Layout Grid block, they overlap the confines of the Layout Grid. Clicking the Reset button next to the size of the image resolves that, though! Transferring to the Block Experiments repo! |
Came across a similar instance here: 4893057-zd-woothemes Tried reproducing this by manually recreating their setup and I wasn't able to, though. Not sure what causes this. |
The same is happening for another user at 4943732-zd-woothemes
The issue is fixed when clicking the Reset button on image size (for only a particular image) |
Thanks for all the reports. It's helpful when you report to include some test content, you can use the Copy all content option from this menu: It would also be helpful if you could test with the Columns block in addition to the layout grid block. If the problem exists in the Columns block, then it is not an issue with the Layout Grid block. From what I can tell, this issue is a duplicate of WordPress/gutenberg#38381. |
Just had a very similar case but this is related to the file block. Reported it separately but here is a link to the GH - #62767 (comment) |
Commenting on #62767 as well. While it relates to the file block, it seems to be the embed (such as PDF embed) on the file block that overlaps, rather than the block itself. |
Similar issue here: 4971561-zd-woothemes Images with specific widths set at the top of each column, create an overlap. This workaround alleviates the issue but isn't intuitive nor fixes the core issue. I was unable to find a fix. Workaround:
Example: https://d.pr/v/nDRWa5 |
Another case here: zd: 5300843 HC: 35813346 User would like to be notified when resolved. |
Another case in 5309192-zd-woothemes User had a Layout Grid nested within a Layout Grid: the inner Grid contained only a Paragraph block, the outer Grid contained Paragraphs and a Tiled Gallery, so the above workaround ("reset" button to reset image sizes) doesn't apply. Removing the nested Layout Grid does work in this instance, though. Click for example block codeUser's content replaced with dummy content:
Note regarding the example code above: you may need to reduce the width of the editor window (shrink browser window and/or open List View and block settings) to see the overlapping. |
Support References This comment is automatically generated. Please do not edit it.
|
📌 SCRUBBING : RESULT
📌 FINDINGS/SCREENSHOTS/VIDEO
📌 ACTIONS
📌 MESSAGE TO QUALITY SQUAD
|
Another case, here 5940293-zd-woothemes |
Quick summary
The Layout Grid Block content is overlapping in the page/post editor but renders as expected on preview/publish.
Steps to reproduce
What you expected to happen
For the Layout Grid Block content in the editor to not overlap.
What actually happened
Layout Grid Block content overlaps in the editor yet appears fine when you preview the page/post.
Context
Customer report: 4877589-zen
Simple, Atomic or both?
Simple
Theme-specific issue?
No. The customer's theme is Radcliff 2. I can replicate the experience on that theme as well as Skatepark.
Browser, operating system and other notes
Customer's notes: "Mozilla / Firefox 98, but I also tried on a 'private window' AND on Google Chrome"
I can replicate it on Chrome (Version 98.0.4758.109 (Official Build) (x86_64))
Testing was done on simple sites.
Reproducibility
Consistent
Severity
Some (< 50%)
Available workarounds?
No response
Workaround details
There are no workarounds I'm aware of. We can reassure customers that the content renders as expected in preview/publish.
The text was updated successfully, but these errors were encountered: