You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the reportAllChanges option is set to true, every metric exposed by this library will early report some value—except for CLS for pages where there are no layout shifts. The implications of this is it's more likely that a page with no CLS will fail to report any value in cases where unload or background detection is unreliable.
For sites that would like to eagerly report metric values and then update them if/when new values are reported, it should be possible to eagerly report zero-CLS.
Note that it can't be assumed that a page that didn't report any CLS had zero CLS, since pages that don't report FCP also do not report CLS. To account for this, I think it makes sense to report a zero-value CLS as soon as FCP is reached.
The text was updated successfully, but these errors were encountered:
If the
reportAllChanges
option is set totrue
, every metric exposed by this library will early report some value—except for CLS for pages where there are no layout shifts. The implications of this is it's more likely that a page with no CLS will fail to report any value in cases where unload or background detection is unreliable.For sites that would like to eagerly report metric values and then update them if/when new values are reported, it should be possible to eagerly report zero-CLS.
Note that it can't be assumed that a page that didn't report any CLS had zero CLS, since pages that don't report FCP also do not report CLS. To account for this, I think it makes sense to report a zero-value CLS as soon as FCP is reached.
The text was updated successfully, but these errors were encountered: