[wp-trac] [WordPress Trac] #44427: Introduce lazy-loading API for media and other elements

[WordPress Trac]

#44427: Introduce lazy-loading API for media and other elements
-------------------------------------------------+-------------------------
 Reporter:  mor10                                |       Owner:  flixos90
     Type:  feature request                      |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.4
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests 2nd-        |     Focuses:
  opinion                                        |  performance
-------------------------------------------------+-------------------------

Comment (by westonruter):

 Replying to [comment:75 mikeschroder]:
 > I'm concerned about this, but from the WordPress side of things. How can
 WordPress know what a user intended -- in particular with previous
 images/themes that weren't aware of this feature? I like the idea if we
 can do it safely -- just want to be sure that I understand what makes
 things different here.
 >
 > A quick note that if it's decided to go ahead with this, I think it
 would benefit from a public proposal so that we can gather feedback from
 the wider community about potential side effects/edge cases.

 What if we restrict adding adding `loading=lazy` by default to just images
 that are being loaded from the install's `uploads` directory? This will
 avoid scenarios where we accidentally lazy-load images that are being used
 for tracking purposes, which would generally be pointing to some external
 domain or to some REST API endpoint.

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