Daniel Holbert

@skobes: right, there's no difference between -100vw and larger values. My concern here is about the fact that we're giving better scores to stuff positioned adjacent to the viewport as...

One option for solving this: we could disregard movement that's outside of a scroll frame's scrollable overflow area. Per https://drafts.csswg.org/css-overflow-3/#scrolling-direction : "UAs must clip the scrollable overflow area of scroll...

> This wasn't actually a "move" after all... > For the user, it appears out of nowhere in both cases, as if it were just added to DOM, and occupies...

> I think the Note in PerformanceTimeline should instead point to https://w3c.github.io/timing-entrytypes-registry/#registry. You can see there the size is 150. Ah, thanks. Yeah, I guess https://w3c.github.io/performance-timeline/ needs a correction on...

(My hypothetical "time-box" musing is sort of a thought about `buffered` in general; it's not specific to layout-shift, aside from the fact that layout-shift seems like it might require a...

> you do not need to compute anything once the buffer is full and there are no observers. Aha, I totally missed this aspect -- I'd misunderstood the buffer as...

I think the main thing that started me wondering about this was this snippet in the explainer: > By passing `buffered: true` to observe, the observer is immediately notified of...

> > you do not need to compute anything once the buffer is full and there are no observers. > > This addresses my concern about imposing a cost on...

Thanks. Yeah, I was musing over those same options (reducing/disregarding `buffered` and/or tracking a somewhat different set of geometric data about repaints that's more readily available). > 4. Change the...

@mmocny: > Trying to summarize this thread: [...] > Could perhaps a Document Policy be used to opt-in to buffering of default-off metrics? Thank you for that summary - that's...