Open patrickhulce opened 4 years ago
Indeed to understand this spec one needs to also look at the Element Timing spec as the method to add the LCP entry is called from there. As you can see renderTime
comes from there too. The explainer of that spec has some information about what it means: https://github.com/WICG/element-timing#what-information-is-exposed
I think what we need to do is augment the LCP explainer and the LCP spec usage example so that this is more clear.
I think what we need to do is augment the LCP explainer and the LCP spec usage example so that this is more clear.
That would be great 👍 the information in that element timing explainer is indeed exactly what I was looking for.
Belatedly getting back to this, it seems like the short term solution is to add a similar pointer to LCP's render time definition. In the longer term, we probably want to fold those two inter-dependent specs into a single one..
I had a difficult time figuring out how
renderTime
was defined for progressively loaded images based on the spec. Right now all therenderTime
links just point to the attribute definitionWhich isn't all that helpful.
Ultimately, the element timing spec example on security was the most helpful to me as it gave the specific example of the next paint after an onload handler.
Maybe there could be a section either defining or linking to the definitions of renderTime for different element types?
edit: this came out of an investigation in Lighthouse which has some interesting cases of LCP there if you're curious :) https://github.com/GoogleChrome/lighthouse/issues/10527