-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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: add new CLS (all frames) to hidden metrics audit #12476
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
impl LGTM
I have the open naming question mostly because I'm not sure where this PR fits in with the overall plan for new CLS. If it's a very temporary thing that will disappear by 8.0, then as-is WFM. If it's being engraved permanently in metrics.js today, then let's chat :)
* @return {number} | ||
*/ | ||
static newCumulativeLayoutShift(layoutShiftEvents) { | ||
const gapµs = 1_000_000; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this was super neat to see, I've seen enough people mistakenly use µs
thinking it's "fancy" millisecond or nanosecond to be minorly concerned about this (not to mention problematic with the fact that all of our camelcase millisecond Ms
are actually indistinguishible from capital Mu Ms
) 😆
how sad would it be to use?
const gapµs = 1_000_000; | |
const gapMicroseconds = 1_000_000; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how sad would it be to use?
not sad at all :)
(not to mention problematic with the fact that all of our camelcase millisecond
Ms
are actually indistinguishible from capital MuMs
)
ah, see, there's the problem. You're still writing M
when clearly you mean Μ
:D
types/artifacts.d.ts
Outdated
@@ -789,6 +789,7 @@ declare global { | |||
layoutShiftMaxSessionGap1sLimit5s: number, | |||
layoutShiftMaxSliding1s: number, | |||
layoutShiftMaxSliding300ms: number, | |||
newCumulativeLayoutShiftAllFrames: number, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't expect new
to be part of the internal name :)
layoutShiftMaxSessionGap1sLimit5sAllFrames
? :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
layoutShiftMaxSessionGap1sLimit5sAllFrames
is good
ha, no, that's very much what I was planning, but I guess I didn't discuss with others more than here and in #12046. Basically live in |
Cool beans, that's what I figured, but wanted to double check just in case :) |
first checkbox of #12350
It should still be easy to copy and paste out of the variants file into the real metric file when the time comes. Doing it now in the
metrics
audit so the tail end of the May HTTP Archive run can pick up some CLS AF data with the new CLS definition.