Comments (4)
I believe the spec is talking about precision in the sense that a small-magnitude change could be expected from a user agent that is implementing the metric, or such deltas can be expected when comparing values between user-agents. This is because the spec provides some flexibility around edge cases and around performance optimizations that may be used to compute the shifts faster. Still, at the scale in which CLS is reported, 0.1 is actually pretty large (I know, not super intuitive), so I still think it makes sense for a developer to aim to be below that threshold while also not paying attention to very small deltas, orders of magnitude smaller than the target. Does this make sense? If so, we can update the spec text so that the intention behind the text is clearer. Let me know what you think!
from layout-instability.
Maybe if we reworded the spec text to something like the following, it'd be clearer that you're intending to talk about precision in the sense of small variations being ignorable?
Something like:
"Developers are advised to avoid reacting to small amounts of variation between layout shift scores; this metric is not intended to be a high-precision value, so user agents might compromise precision in the interest of calculation efficiency. Moreover, the definition of the metric may evolve over time."
(I don't love the word "reacting" here, but I can't think of a better word off the top of my head.)
from layout-instability.
s/reacting to/worrying about? I like the suggestion, thanks!
from layout-instability.
Sure, that sounds good. Thanks!
from layout-instability.
Related Issues (20)
- CumulativeLayoutShift as WPT custom metric empty HOT 1
- Update CLS to window-based
- Specify layout shifts during drag HOT 2
- Explain expectations for content which shifts while fully obscured by other content (i.e. covered by a fixed position z-index overlay)
- Resolve confusion from equal previous/current rects
- Input Exclusion (lastInputTimestamp and hadRecentInput) should include certain interactions with Browser UI. HOT 1
- The definition of DCLS and CLS (non-normative) should mention ignoring shifts with hadRecentInput: True
- Broken references in Layout Instability API
- Clarify value of entry.name: empty string or "layout-shift"
- Layout shift reported without actual visual shifting for resized fixed iframe HOT 4
- exclude elements that transition from hidden to visible HOT 4
- CLS issue caused by FIXED position elements having z-index HOT 2
- Clarification about Hover causing layout shift HOT 2
- `content-visibility: auto;` makes CLS go bananas HOT 2
- Consider excluding user-scroll + scroll-anchor in the same frame from being penalized HOT 1
- What events trigger LayoutShift Performance Callback? HOT 2
- Starting point shift with countering transform change should be ignored HOT 1
- Change events should also trigger hadRecentInput
- ignore inline-direction shift in/out of view
- Case of sticky sidebars changing from absolute to fixed HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from layout-instability.