Add Lifecycle State monitoring and manipulation to chrome devtools>Application |
|||
Issue descriptionRecently, we have introduced PageLifecycle a notion of page lifecycle state for the web. https://wicg.github.io/page-lifecycle/spec.html Most of the transition of the pages are decided by the browser, so web developers cannot easily test their applications for different lifecyle states. Web Developers now can use the chrome://discards UI to change some of these states, but it would be better if it is included in the DevTools-Application tab instead. Parts of the PageLifecycle is already exposed via the RDP protocol.
,
Aug 27
Thanks for checking in. It is relatively high priority to actually support automated testing - captured in crbug/837709 (I'll add you to a thread where we are discussing the infra changes needed there, would appreciate your input). I think this bug primarily captures DevTools support for what is already possible from chrome://discards. This issue is low priority, unless we hear otherwise from web devs.
,
Sep 12
,
Dec 4
We can re-file it when it becomes interesting again. |
|||
►
Sign in to add a comment |
|||
Comment 1 by pfeldman@chromium.org
, Aug 27