New issue
Advanced search Search tips

Issue 371690 link

Starred by 7 users

Issue metadata

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

Blocking:
issue 901609



Sign in to add a comment

Support navigator.serviceWorker in WorkerNavigator

Project Member Reported by kinuko@chromium.org, May 9 2014

Issue description

Support navigator.serviceWorker in dedicated worker

I think this is not critical / no need to target M37 unless someone strongly requests it.

Filing this just to keep some notes and pointers:
* We'll need to implement WorkerNavigatorServiceWorker.cpp and related code in blink (most of plumbing should be already there)
* r269102 intentionally killed some dedicated worker specific code, https://codereview.chromium.org/261533003/#ps100001 is the last version I hacked that includes code for dedicated workers

 issue 366538  has some more context about why dedicated worker support is not that easy. (The architecture is still changing / will change over the time so when we resume the discussion may no longer be relevant, but anyway)

 
Project Member

Comment 1 by bugdroid1@chromium.org, Nov 11 2014

The following revision refers to this bug:
  http://src.chromium.org/viewvc/blink?view=rev&rev=185090

------------------------------------------------------------------
r185090 | kinuko@chromium.org | 2014-11-11T02:02:45.248233Z

Changed paths:
   M http://src.chromium.org/viewvc/blink/trunk/Source/web/WorkerGlobalScopeProxyProviderImpl.cpp?r1=185090&r2=185089&pathrev=185090

Don't create ServiceWorker provider in dedicated workers (yet)

We don't expose ServiceWorker in WorkerNavigator yet, and creating
a provider for workers could cause data-race with the current code.
(See https://code.google.com/p/chromium/issues/detail?id=423107#c8 for
more details)

BUG= 423107 ,371690
R=michaeln

Review URL: https://codereview.chromium.org/717553003
-----------------------------------------------------------------
Cc: nhiroki@chromium.org
(I'm interested in supporting navigator.serviceWorker in service worker)

Comment 3 by falken@chromium.org, Apr 16 2015

Labels: -Pri-3 Pri-2 M-47

Comment 4 by falken@chromium.org, Apr 16 2015

Labels: Cr-Blink-Workers

Comment 5 by falken@chromium.org, Apr 21 2015

Cc: kinuko@chromium.org
 Issue 455593  has been merged into this issue.
Blocking: chromium:532989

Comment 7 by falken@chromium.org, Oct 26 2015

Labels: -M-47

Comment 8 by falken@chromium.org, Jun 21 2016

Summary: Support navigator.serviceWorker in WorkerNavigator (was: Support navigator.serviceWorker in dedicated worker)
Project Member

Comment 9 by sheriffbot@chromium.org, Jun 21 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)

Comment 11 by awdf@chromium.org, Jul 4 2017

Blocking: -532989
This has potentially troublesome possibilities about a service worker registering a SW which registers a SW etc etc etc resulting in a SW essentially keeping itself alive forever. We should think twice before implementing this.
> This has potentially troublesome possibilities about a service worker registering a SW which registers a SW etc etc etc resulting in a SW essentially keeping itself alive forever.

Is there a spec issue for this problem yet?  Perhaps we could just reject register() with TypeError if called from a service worker.  Other workers created from a window would be permitted to call it.

Comment 14 by mek@chromium.org, Aug 7 2017

I filed https://github.com/w3c/ServiceWorker/issues/1117 a couple of months ago for this.
Project Member

Comment 15 by sheriffbot@chromium.org, Aug 7

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
(SW bug triage)
Blocking: 901609

Sign in to add a comment