Nicolás Peña Moreno
Nicolás Peña Moreno
It's not feasible to expose every contentful paint. It would be possible to expose a contentful paint after a given point in time, and if the use case is for...
Page Visibility only has an event handler for visibility change. It does not say what the previous visibility state was, and to use in this case would require early event...
The only problem with ThrottlingEntry is that it would be harder to specify. I would propose starting with page visibility (possibly adding out-of-viewport), which would likely cover most cases?
PageVisibility observer will be able to address the concern of this bug. I agree that exposing throttling signals and such is a more tricky subject since it's not even well...
For the purposes of validation of paint metrics, throttling is irrelevant and visibility needs to be exposed. But it's true that there are other uses-cases for which network or CPU...
A summary of recent discussions: - In Oct 8 [meeting](https://docs.google.com/document/d/1DC7dvpwS68gxTYOgXQ43pn5iHzJ66FlT21EJ-ba-eow/edit), we discussed https://github.com/w3c/page-visibility/issues/59 and some ideas surfaced about having a third state to cover prerendering and possibly mobile states that...
> FWIW pageVisibility itself is somewhat fuzzily specified (and overly desktop-centric) - it doesn't sound crazy to me to give some similar amount of wiggle room to UAs to also...
Hmm is this just a question? :) I guess I'm not sure what the answer here should be, and if we do want to surface them then we'd want to...
Several questions come to mind: - If we wanted to expose this to RUM, what would be a sensible security model to do so? - Is it possible to compute...
Just wanted to ping this to ask: are you aware of any potential customers for this data? Also adding @spanicker as this seems related to their problems of finding the...