New issue
Advanced search Search tips

Issue 618531 link

Starred by 2 users
Status: Duplicate
Merged: issue 593320
Owner: ----
Closed: Jun 2016
Cc:
pfeldman@chromium.org
mmenke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Feature



Sign in to add a comment

service worker doesn't work with offline by network throttling

Reported by block.rx...@gmail.com, Jun 9 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce the problem:
1. emulate offline using network throttling in dev tools
2. add service worker
3. register backgroundsync event

What is the expected behavior?
sync event fires immediately after registering even if make it offline using network throttling

What went wrong?
when PC is offline, sync event will fire when PC will be online.
so it expected that network throttling same.

Did this work before? N/A 

Chrome version: 50.0.2661.102  Channel: n/a
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 21.0 r0

if sync ui for service worker and network throttling works as same as real behavior will help us developing.

Comment 1 by rsleevi@chromium.org, Jun 9 2016

Cc: pfeldman@chromium.org mmenke@chromium.org
Components: Blink>ServiceWorker
Labels: -Type-Bug Type-Feature
Given that DevTools' throttling is per-tab (intentionally), but that ServiceWorkers are inherently tab agnostic, I believe this is "WorkingAsIntended"

https://groups.google.com/a/chromium.org/d/msg/net-dev/BnlOAnLwZOk/v8qLJDZKBwAJ has a bit more context.

Comment 2 by jonathan.garbee@chromium.org, Jun 9 2016

Mergedinto: 593320
Status: Duplicate (was: Unconfirmed)

Comment 3 by block.rx...@gmail.com, Jun 9 2016 

that's sounds reasonable, but not not intuitive for me that window is offline while controller is online.
so how about adding offline for service worker ?
it will help us to develop offline app with out triggering PC wifi setting.

Comment 4 by falken@chromium.org, Jun 9 2016 

comment #3: This bug was marked a duplicate of  issue 593320 . Does that issue cover this bug for you?
►

Sign in to add a comment