Skip to content

Instantly share code, notes, and snippets.

@skobes-chromium

skobes-chromium/layout-stability-metric.md

Last active April 25, 2021 05:40
Show Gist options
  • Save skobes-chromium/2f296da1b0a88cc785a4bf10a42bca07 to your computer and use it in GitHub Desktop.
Save skobes-chromium/2f296da1b0a88cc785a4bf10a42bca07 to your computer and use it in GitHub Desktop.
Download ZIP
@tdresser
Copy link

tdresser commented Feb 6, 2019

We don't expect the average web developer to touch this API. The common case here will be for RUM analytics vendors to surface this data to users, highlighting issues the developer wasn't aware they had.

You're right that actionability is sometimes tricky here, but the first objective is to make sure developers realize there's a problem. Once developers know there's a problem, we can tackle actionability via:

  • Documentation (e.g., try enabling the unsized media policy and set your font-display values to optional).
  • Local developer tooling letting devs dig in further, with more actionable output.
  • Possibly in the future, better attribution baked into the layout stability API.

Does that seem reasonable? I think step 1 is ensuring folks are aware of the problem and step 2 is making it simple to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment