Ilya Grigorik

> I know —thank you @hteumeuleu for this tweet— that IE11 and Edge already support a lazyload attribute, but they are alone and the draft spec has been abandonned, inviting...

> I think CPP should let us manage both separately, even if they overlap a little. See https://discourse.wicg.io/t/a-standard-way-to-lazy-load-images/1153/12.

> Without client-side validations, it's unclear to me if one would be able to get and maintain an accurate picture of what's happening in the wild. Slightly orthogonal, but another...

A quick summary of the points raised in the above exchange (because twitter threading is full of fail): - @paullewis @jakearchibald both highlighted that raF polling only captures the main...

> Please explain why every script would have to set up its own polling. I envisioned my script as a generic one that just keeps track of current performance, and...

@spite that Twitter thread seems to indicate that the difference is ~0.05ms; what am I missing? Do you have a list, or pointers, to concrete cases where rAF estimates led...

> Taking a step back, I think the things we want to capture are: > - Time from specific action to related rendering update > - Rendering update average &...

> Aren't these attacks already open? It's not just a question of whether it's possible but also how accurate and quickly it can be executed. Explicit feedback on when a...

@KenjiBaheux I think that's spot on. My only nitpick would be with the last 500ms timer logic: > set a race between a (500ms - performance.now()) timeout and a Font...

@tabatkins consistent with respect to what? I think both start times are valid (navStart, requestStart) and have their respective use cases. That said, I think navigationStart is what developers would...