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

Issue 606959 link

Starred by 1 user
Status: Duplicate
Merged: issue 632823
Owner:
falken@chromium.org
Closed: Aug 2016
Cc:
jakearchibald@chromium.org
slightlyoff@chromium.org
█ kenjibaheux@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Service Worker is started for page, even if JavaScript is blocked

Project Member Reported by jww@chromium.org, Apr 26 2016 
Version: 50.0.2661.86
OS: Linux

What steps will reproduce the problem?
(1) Visit a site with JavaScript and a Service Worker, for example https://joelweinberger.us.
(2) Confirm that Service Worker has installed.
(3) Block JavaScript for that host using content settings or the origin info bubble.
(4) Reload site and note that the Service Worker still executes while other scripts are blocked. On https://joelweinberger.us, this can be noted by the console message "Running ServiceWorker" which is logged from the SW, even when JS is blocked, while the "registering service worker..." message only appears when JavaScript is not blocked.

What is the expected output?
The Service Worker for the origin would not execute if the content setting disables JavaScript for that host.

What do you see instead?
The Service Worker executes.

Please use labels and text to provide additional information.

Comment 1 by falken@chromium.org, Apr 27 2016

Labels: M-52

Comment 2 by mea...@chromium.org, May 3 2016 

Joel: Are you still seeing this on canary?
Blocking JS and reloading the page was problematic in that some parts of the page still executed while the page kept loading.  https://crbug.com/232410  fixed that, and from a brief testing it seems to have fixed this bug too.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by falken@chromium.org, Jul 12 2016

Labels: -Pri-1 Pri-3
Summary: Service Worker is started for page, even if JavaScript is blocked (was: Service Worker executes on page, even if JavaScript is blocked)
Yes it looks like the SW is not able to execute script when JS is blocked.

However, we still do start the worker and it's listed as "running" in DevTools.

We might be more clever and bypass starting the worker if JS is blocked.
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 12 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by shimazu@chromium.org, Aug 12 2016

Mergedinto: 632823
Status: Duplicate (was: Assigned)
►

Sign in to add a comment