Khushal Sagar

I actually prefer (1) without making it VT-specific. It could be a counterpart to the `navigate` event in the navigation API except this one is not cancellable. The con with...

Thanks for clarifying @smaug----. Do you have thoughts on the other point: "rendering a frame after pagehide"? Would that mismatch developer expectations of how pagehide behaves today?

> But, do we want that the extra rendering triggers all the relevant callbacks? We need the update the rendering loop to run for snapshots. That's because if the author...

> Why would there be async step between firing pagehide and marking page hidden. We can have a rendering step there if we want. Because update-the-rendering steps run on a...

> I'm just saying that it would be possible, if we want that. Its way too complicated to support in Chromium. We have a pull model where the compositor pulls...

Thanks. LGTM!

Other than the visibility based throttling @szager-chromium mentioned, `content-visibility` is the other reason I could find for it (@vmpstr for it). The throttling done for view transitions is already carved...

I'm wondering if content-visibility is a good concept to build on for this throttling; since the goal is similar: minimize rendering cost of content not *relevant* to the user (as...