New issue
Advanced search Search tips

Issue 831876 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Refine keep-active signal to be more granular

Project Member Reported by panicker@chromium.org, Apr 11 2018

Issue description

Currently we have a single "keep-active" signal that covers fetch, service worker and shared worker needing to keep the renderer active (not frozen)
Ideally we would have more granular signals that freeze specific task queues: 
- pending fetch-keepalive should only unfreeze loading (and freeze other queues).
- service worker should ideally have its own task queue and allow freezing everything else
 
 
Cc: fmea...@chromium.org
We particularly want 
- pending fetch-keepalive should only unfreeze loading
for the case where we call fetch-keepalive from within onfreeze, and after the onfreeze callback, we should not run any tasks except those needed for that fetch request.
Labels: -Type-Bug Type-Feature

Sign in to add a comment