[wp-trac] [WordPress Trac] #52768: WordPress post URL oEmbed rendering blocked by iframe lazy-loading

[WordPress Trac]

#52768: WordPress post URL oEmbed rendering blocked by iframe lazy-loading
---------------------------+--------------------------
 Reporter:  SirStuey       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  5.7.1
Component:  Embeds         |     Version:  5.7
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:  performance
---------------------------+--------------------------

Comment (by SirStuey):

 Replying to [comment:13 peterwilsoncc]:
 > I say this reluctantly, but I am wondering if the iframe lazy loading
 ought to be reverted while a solution is figured out.

 Have there been any other bug reports or wordpress.org support requests
 regarding embeds other than those related to WordPress post (or product)
 embeds?

 If the iframe lazy loading update is reverted, would there be a timeline
 for its reimplementation? Even if the WordPress embed conflict is not
 resolve, it is still beneficial to have built-in lazy loading of other
 types of embeds, such as YouTube links.

 There's not a lot of speed to be gained by lazy-loading Wordpress embeds,
 but there is a lot to be lost by not lazy-loading embedded YouTube videos.

 Respectfully, speaking personally, I'd prefer to keep lazy-loading. It
 seems to work well, and Felix's customization script has everything on my
 site displaying properly until either a patch or reversion is settled on.
 But, I also typically only embed my own Wordpress posts, or URLs from
 popular social media or video hosting platforms. I'm not fully versed with
 how others might embed Wordpress posts.

 Lazy-loading YouTube iframes was already on my to-do list ahead of
 Google's May speed-based algorithm changes.

 [comment:8 peterwilsoncc]:
 > I'm a little worried such a targeted fix would miss other affected
 embeds, either WP native or added via raw HTML by a user with the
 `unfiltered_html` capability.

 If there exists the strong potential for unanticipated behaviors, would it
 be practical to instead designate a limited list of included URL embed
 iframes to be given lazy loading?

 (Thank you both very much for your attention to this!)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52768#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform