Open ryantownsend opened 1 year ago
I think that WICG/element-timing might be the place to fix this, since LCP (mostly) builds on top of that spec, and an image with elementtiming
set which happens to use this directive should report the correct timing info there as well.
I think that WICG/element-timing might be the place to fix this, since LCP (mostly) builds on top of that spec, and an image with
elementtiming
set which happens to use this directive should report the correct timing info there as well.
We need to merge the two specs, tbh.. We'll discuss that at TPAC.
As per web.dev, elements with background images are considered LCP candidates, but only when using
url()
:However, we now have
image-set()
and the upcomingimage()
(hat-tip @schepp) which are alternative methods of loading background images with additional functionality (e.g. content-type selection), so the LCP spec should be updated to consider these as valid candidates also.I have two test pages to demonstrate the behaviour by simply swapping
url()
forimage-set()
in the CSS:url()
image-set()
Update: I've logged a parallel Chromium bug to address the implementation