-
Notifications
You must be signed in to change notification settings - Fork 4.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
Query Loop: Show Featured Image placeholders in all posts #49301
Query Loop: Show Featured Image placeholders in all posts #49301
Conversation
Size Change: +4 B (0%) Total Size: 1.34 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix works as expected!
An alternative would be to show all placeholders that are currently hidden in these previews(useBlockPreview).
We can only hide placeholders without illustrations - .components-placeholder:not(.has-illustration)
.
But I like the idea of progressive fixes for placeholders. Not every block needs to display a placeholder state in previews.
Flaky tests detected in 8789e6b. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4499554990
|
Thanks for fixing this up @ntsekouras!
This is a really interesting case, I think it reveals that we sort of have two different categories of placeholders when it comes to block previews.
From a bit of digging, I think the issue here might have been introduced back in #41605 where the placeholder illustrations were moved from being output directly, to forming part of the
I agree with @Mamaduka here, I think it makes sense for blocks to explicitly determine when they should display placeholders in previews. But, we can always revisit that assumption if we wind up having to fix up more blocks 🙂 |
What?
Fixes: #49167
How?
I actually just added the style change for this block. An alternative would be to show all placeholders that are currently hidden in these previews(
useBlockPreview
). @andrewserong might have some context why he introduced this style.Testing Instructions