-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
core(cls): shorten description #10570
Conversation
i think we can drop the scoring bit. the learnmore link covers that. here's my attempt at a really terse explanation:
|
i raise you this |
I'll cede this one to @paulirish |
works for me. |
wording was a little awkward and I didn't like reusing 'layout'
|
Now i'm not so sure about this :) "how much" causes a miscue for me while reading, where I think the thing immediately after it is what's being measured, then it reads like a grammar error ("how much visible elements?") and then I realize "move" is what is being measured, but by then I've lost the flow. If we want to keep this general form, something like
(or within the viewport, etc) could also work. |
sure. i like:
|
It's a bit long ...
I shortened it without removing any information - simplified the grammar constructs (
being a ...
is a longer way to sayis
).Further ideas for simplification / changes:
0.5 seems like a high range. even 0.33 looks "highly shifting"
"between 0 and 1" is not true. CLS can be >1.