-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cumulative Layout Shift #386
Comments
To clarify, the specification would be https://wicg.github.io/layout-instability/ since CLS is not exposed directly but can be computed based on the layout shifts exposed by the Layout Instability API. We can add a section dedicated to CLS if it helps. |
@npm1 yes, it would be helpful to have a section to CLS and how it's computed in the proposal, as editable text, just because that will clarify and guide future work. |
[EDIT: I removed this comment and spun it off as WICG/layout-instability/issues/57 , "The spec disagrees with developer documentation about whether precise layout-shift values/thresholds should be relied on"] |
In WICG/layout-instability#58, the spec for the Layout Instability API has been updated with further details in non-normative text about the definition of CLS. |
Request for Mozilla Position on an Emerging Web Specification
Other information
One of 3 metrics defined by Google's Web Vitals in 2020. See: https://web.dev/vitals/
This depends on the layout instability API, for which there is a separate issue #374.
More detailed specs of 'layout-shift-score' and links to canonical sources will be added as comments to this issue.
The text was updated successfully, but these errors were encountered: