Re: [w3ctag/design-reviews] Layout Instability Metric (#393)

These are good questions to think about.  It's already possible for a site to query an element's bounding rect, but it is infeasible to query every element at every point in time.  So I would say the metric enables observing layout changes in a way that isn't efficient today.

The explainer contains some comments under "Privacy and Security" about the possible use of the API for fingerprinting, and about cross-origin subframe restrictions which the API respects.

If you have other ideas about unexpected capabilities the API might enable I would be interested in hearing about them.

I think a rough guideline on scoring might be
0.0 - 0.1 = low jank
0.1 - 0.5 = medium jank
0.5 - 1.0 = high jank

Scores above 1.0 are possible but the differences become less meaningful.  (The highest scores tend to be sessions with auto-repeating layout-inducing animations.)

I expect we'll refine our understanding of this over time based on the data we observe in the wild.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/393#issuecomment-512236985