-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
wp-block-post-featured-image missing the lazy attribute #41783
Comments
I remember seeing a discussion somewhere that featured-images should not get the lazy attribute, because usually they are above the fold, and lazy-loading them is bad for performance and the user-experience... 🤔 |
I remember that discussion but when in a page there is more then one? |
An example would be an archive of posts, where each post has its featured image inside the query loop 😉 |
Potentially related Trac ticket: https://core.trac.wordpress.org/ticket/56930. |
Related: #45224 |
@Mte90 @aristath @ockham @spacedmonkey https://core.trac.wordpress.org/ticket/56930 is primarily caused by https://core.trac.wordpress.org/ticket/55996, which is also covered in #45224 and now has a working (core) PR in WordPress/wordpress-develop#3549. The problem here is a different one though: I'm unsure whether the original issue description is accurate - the I believe there is something we need to tweak in the |
I found the problem here and addressed it as part of WordPress/wordpress-develop#3560: Basically, the issue with the |
Fixed via #45534. To follow the wider-reaching WP core fix, please follow along https://core.trac.wordpress.org/ticket/56930. |
Description
Since WP 5.5 the lazy attribute to img tags is added automatically.
Well this block doesn't have that value...
gutenberg/packages/block-library/src/post-featured-image/edit.js
Line 152 in ba9b739
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
No response
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: