New issue
Advanced search Search tips

Issue 801036 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 797222
Owner: ----
Closed: Jan 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 715640



Sign in to add a comment

S13nServiceWorker: make sure the worker is started when ControllerServiceWorker interface ptr is queried or sent by/to the clients

Project Member Reported by kinuko@chromium.org, Jan 11 2018

Issue description

S13nServiceWorker: make sure the worker is started when ControllerServiceWorker interface ptr is queried or sent by/to the clients.

Currently clients (are going to) have two ways to get the interface ptr to ControllerServiceWorker:

1. Clients can call SWContainerHost::GetControllerServiceWorker() to get the interface ptr. The method is implemented by SWProviderHost in the browser process, and clients usually call it via ControllerServiceWorkerConnector (during subresource loading).

2. Clients can get a new controller ptr when the browser calls SWContainer::SetController() after https://chromium-review.googlesource.com/c/chromium/src/+/742961 lands. The method is called by SWProviderHost in the browser process, and implemented by SWProviderContext in the renderer.

In both cases we should make sure the service worker is running or is starting up, so that the interface ptr is going to work (or connection error happens if the request is dropped).
 

Comment 1 by kinuko@chromium.org, Jan 11 2018

Mergedinto: 797222
Status: Duplicate (was: Available)
Oops, dup'ed.

Sign in to add a comment