New issue
Advanced search Search tips

Issue 739906 link

Starred by 4 users

Issue metadata

Status: Archived
Owner:
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

DevTools > Sources does not list service workers, unable to step through code

Reported by stefcame...@gmail.com, Jul 6 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Create a simple HTML page that registers a simple service worker.
2. Open DevTools > Sources

What is the expected behavior?
I expect to see two top-level items:
1. "top"
2. "serviceworker.js" (name of my registered service worker JS file)

What went wrong?
"serviceworkers.js" is not listed, unlike on Windows where it is listed.

On Windows, I'm using Chrome Stable, Version 59.0.3071.115 (Official Build) (64-bit).

Did this work before? N/A 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 16.04
Flash Version: Shockwave Flash 26.0 r0

Debugging service workers in Chrome Linux seems really difficult. It just doesn't work the same way as it does in Chrome Windows/macOS.

What's more, I'm unable to set breakpoints in my service worker and have them hit and step through code. It doesn't even work when I use a 'debugger;' statement.

Perhaps that's a separate issue, which I'm happy to report separately. Please let me know if I should do that. It all seems related to the same basic issue of service worker debugging support lacking on Chrome Linux.
 
index.html
154 bytes View Download
serviceworker.js
62 bytes View Download
devtools-linux.png
77.2 KB View Download
devtools-win10x64.png
29.8 KB View Download

Comment 1 by alph@chromium.org, Jul 10 2017

Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Owner: kozy@chromium.org

Comment 3 by kozy@chromium.org, Dec 8 2017

Status: Archived (was: Assigned)
I believe that we fixed most service workers issues and they should work fine in current stable and latest Canary.

Sign in to add a comment