Nicolás Peña Moreno

I'm not very familiar with `decode()`, but it seems like it might expose that too. We could consider removing the TAO requirement if that API is not going to be...

It does apply for it! See this test for example: https://github.com/web-platform-tests/wpt/blob/master/element-timing/multiple-background-images.html Do you think this needs further clarification in the spec?

Yep, that seems like a different issue. I agree that we should be more specific about the fact that we only observe background images associated to a URL. I don't...

No, thank you for the feedback :) PR is welcome.

Thanks for the feedback! Interesting, anonymous layout objects are definitely a problem here. Any suggestions on how we can fix this? For example, could we consider the nearest element ancestor?

Parent elements does not work like we'd like it to, for example consider the following paragraph: `See the link.` We want link to be grouped with p, hence why we...

Hi, thanks for the issue! Basing it on the 'initial viewport' might have the problem of us not knowing the real image size at the time (not sure about this)....

I'll address the original issue on the LCP side by scaling the size by `min(display_size, intrinsic_size) / display_size`. Regarding the background-size not being captured in Chrome comment, can you file...

I think generally it's hard to determine the 'initial viewport'. Chrome tries to paint quickly at the beginning of the page load, which means we might not even have fully...

Oh hmm reading more what `fully decodable` says I think it implies that the image is ready to be decoded but is not necessarily decoded yet, so I don't think...