New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 755838 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 755861
Owner:
Email to this user bounced
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 629701



Sign in to add a comment

Impl mojo interface ServiceWorkerContainer

Project Member Reported by leon....@intel.com, Aug 16 2017

Issue description

This is to track all the work to implement ServiceWorkerContainer mojo interface.
"
Roughly corresponds to navigator.serviceWorker. Actually needed for anything that could access a ServiceWorkerRegistration/ServiceWorker. E.g., SW needs this since it has self.registration, even though we don’t implement navigator.serviceWorker for Worker yet. But eventually anything that can touch these objects should be a ServiceWorkerContainer, so it’s OK to use this name.

When the browser initialized the navigation or SW startup, it should send the SWContainer along.

interface ServiceWorkerContainer {
  SetController(ServiceWorkerObject controller);
  ServiceWorkerStateChanged(ServiceWorkerObject);
  ServiceWorkerRegistrationUpdateFound(ServiceWorkerRegistrationObject)
  PostMessage();
};
"
 
Cc: -falken@chromium.org -kinuko@chromium.org -leon....@intel.com -shimazu@chromium.org
Mergedinto: 755861
Status: Duplicate (was: Started)
Sorry for making a copy of existed issue

Sign in to add a comment