New issue
Advanced search Search tips

Issue 830325 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 20
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-07-15
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

When i access google docs in offline mode, i need refresh(f5) to see docs.

Reported by ehdeo...@gmail.com, Apr 9 2018

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10452.42.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.79 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Setting offline mode in google drive
2. turn-off wifi
3. access any documents from file app -> google drive -> offiline tab

What is the expected behavior?
I can see offline docs in offline mode

What went wrong?
Error message is shown.
"There is no Internet connection"

Then if i refresh the page by press f5, i can see the document.

Did this work before? N/A 

Chrome version: 66.0.3359.79  Channel: beta
OS Version: 10452.42.0
Flash Version:
 

Comment 1 by mmenke@chromium.org, Apr 11 2018

Components: -Internals>Network Blink>ServiceWorker Platform>Apps
Not sure if this is using an app or service worker for offline mode.

Comment 2 by ehdeo...@gmail.com, Apr 12 2018

Hi.
Here is recording file.
After turn off wifi, i opened google doc in file apps.
Apr 12 2018 10_54 AM.webm
5.5 MB View Download

Comment 3 by ehdeo...@gmail.com, Apr 12 2018

And I remember that there is no problem when using R64, R65.

Comment 4 by bashi@chromium.org, Apr 13 2018

Hi,

Could you give us the content of chrome://serviceworker-internals/ at repro step 3 and after refreshing the page?

Comment 5 by ehdeo...@gmail.com, Apr 13 2018

Hi bashi,
I don't know this is what you need.

Here is content at repro step 3


Registrations in: /home/chronos/u-15bf8a0d86582a81e23d662502611702dc803da0 (3)
Scope: https://drive.google.com/drive
Registration ID: 1
Navigation preload enabled: false
Navigation preload header length: 0
Active worker:
Installation Status: ACTIVATED
Running Status: STOPPED
Fetch handler existence: EXISTS
Script: https://drive.google.com/drive/serviceworker.js?ouid=u7d65efeba9d1fc2d
Version ID: 5
Renderer process ID: 0
Renderer thread ID: -1
DevTools agent route ID: -2
Log:

 
Scope: https://drive.google.com/
Registration ID: 2
Navigation preload enabled: false
Navigation preload header length: 0
Active worker:
Installation Status: ACTIVATED
Running Status: STOPPED
Fetch handler existence: EXISTS
Script: https://drive.google.com/drive/serviceworker_root.js?ouid=u7d65efeba9d1fc2d
Version ID: 4
Renderer process ID: 0
Renderer thread ID: -1
DevTools agent route ID: -2
Log:

 
Scope: https://www.google.co.kr/_/chrome/
Registration ID: 0
Navigation preload enabled: false
Navigation preload header length: 0
Active worker:
Installation Status: ACTIVATED
Running Status: STOPPED
Fetch handler existence: EXISTS
Script: https://www.google.co.kr/_/chrome/newtab-serviceworker.js
Version ID: 3
Renderer process ID: 0
Renderer thread ID: -1
DevTools agent route ID: -2
Log:

Console: {"lineNumber":0,"message":"The FetchEvent for \"https://www.google.co.kr/_/chrome/newtab?rlz=1CASMAK_enKR791KR791&ie=UTF-8\" resulted in a network error response: the promise was rejected.","message_level":2,"sourceIdentifier":1,"sourceURL":""}
Console: {"lineNumber":0,"message":"Uncaught (in promise) TypeError: Failed to fetch","message_level":3,"sourceIdentifier":1,"sourceURL":"https://www.google.co.kr/_/chrome/newtab-serviceworker.js"}
Console: {"lineNumber":0,"message":"The FetchEvent for \"https://www.google.co.kr/async/newtab?ei=CnHQWvX4NceF8gXFg7_gCQ&yv=3&async=xid:1,_fmt:json\" resulted in a network error response: the promise was rejected.","message_level":2,"sourceIdentifier":1,"sourceURL":""}
Console: {"lineNumber":0,"message":"Uncaught (in promise) TypeError: Failed to fetch","message_level":3,"sourceIdentifier":1,"sourceURL":"https://www.google.co.kr/_/chrome/newtab-serviceworker.js"}
Console: {"lineNumber":0,"message":"The FetchEvent for \"https://www.google.co.kr/gen_204?atyp=csi&ei=CnHQWvX4NceF8gXFg7_gCQ&s=newtab&adh=&dlm=Infinity&conn=wifi&ima=1&ime=0&imeb=0&imeo=0&mem=ujhs.10,tjhs.12,jhsl.2060&rt=aft.83,ol.138,prt.6,xjs.59,xjsee.59,xjses.33,xjsls.15,wsrt.83,cst.0,dnst.0,rqst.10,rspt.5,rqstt.11,unt.2,cstt.2,dit.91&zx=1523609901720\" resulted in a network error response: the promise was rejected.","message_level":2,"sourceIdentifier":1,"sourceURL":""}
Console: {"lineNumber":0,"message":"The FetchEvent for \"https://www.google.co.kr/gen_204?atyp=csi&ei=CnHQWvX4NceF8gXFg7_gCQ&s=newtab&action=perf&dlm=Infinity&conn=wifi&ima=1&ime=0&imeb=0&imeo=0&mem=ujhs.10,tjhs.12,jhsl.2060&rt=aft.83,nti.49,fbd.52,thd.54,dbi.70,mvtr.145,wsrt.85,cst.0,dnst.0,rqst.10,rspt.5,rqstt.11,unt.2,cstt.2,dit.91&zx=1523609901726\" resulted in a network error response: the promise was rejected.","message_level":2,"sourceIdentifier":1,"sourceURL":""}
Console: {"lineNumber":0,"message":"Uncaught (in promise) TypeError: Failed to fetch","message_level":3,"sourceIdentifier":1,"sourceURL":"https://www.google.co.kr/_/chrome/newtab-serviceworker.js"}
Console: {"lineNumber":0,"message":"Uncaught (in promise) TypeError: Failed to fetch","message_level":3,"sourceIdentifier":1,"sourceURL":"https://www.google.co.kr/_/chrome/newtab-serviceworker.js"}
Console: {"lineNumber":0,"message":"The FetchEvent for \"https://www.google.co.kr/gen_204?atyp=i&ct=nfkbx&cad=&ei=CnHQWvX4NceF8gXFg7_gCQ&zx=1523609903778\" resulted in a network error response: the promise was rejected.","message_level":2,"sourceIdentifier":1,"sourceURL":""}
Console: {"lineNumber":0,"message":"Uncaught (in promise) TypeError: Failed to fetch","message_level":3,"sourceIdentifier":1,"sourceURL":"https://www.google.co.kr/_/chrome/newtab-serviceworker.js"}
Console: {"lineNumber":0,"message":"The FetchEvent for \"https://www.google.co.kr/gen_204?atyp=csi&ei=CnHQWvX4NceF8gXFg7_gCQ&s=async&astyp=newtab&rt=fr.2,ft.9331&zx=1523609910991\" resulted in a network error response: the promise was rejected.","message_level":2,"sourceIdentifier":1,"sourceURL":""}
Console: {"lineNumber":0,"message":"The FetchEvent for \"https://www.google.co.kr/gen_204?atyp=csi&ei=CnHQWvX4NceF8gXFg7_gCQ&s=newtab&action=update&dlm=Infinity&conn=wifi&ima=1&ime=0&imeb=0&imeo=0&mem=ujhs.10,tjhs.12,jhsl.2060&rt=aft.1,xhrf.9335,wsrt.167,cst.0,dnst.0,rqst.10,rspt.5,rqstt.11,unt.2,cstt.2,dit.91&zx=1523609910998\" resulted in a network error response: the promise was rejected.","message_level":2,"sourceIdentifier":1,"sourceURL":""}
Console: {"lineNumber":0,"message":"Uncaught (in promise) TypeError: Failed to fetch","message_level":3,"sourceIdentifier":1,"sourceURL":"https://www.google.co.kr/_/chrome/newtab-serviceworker.js"}
Console: {"lineNumber":0,"message":"Uncaught (in promise) TypeError: Failed to fetch","message_level":3,"sourceIdentifier":1,"sourceURL":"https://www.google.co.kr/_/chrome/newtab-serviceworker.js"}

 

Comment 6 by ehdeo...@gmail.com, Apr 13 2018

Sorry for mistake.
I check content once again like below.
 1) Open doc in offline mode
 2) Open chrome://service~~~ then copy the content
 3) Refresh the doc
 4) Refresh chrome://servie~~ page then copy 

At step3
ServiceWorker
Registrations in: /home/chronos/u-15bf8a0d86582a81e23d662502611702dc803da0 (3)
Scope: https://drive.google.com/drive
Registration ID: 1
Navigation preload enabled: false
Navigation preload header length: 0
Active worker:
Installation Status: ACTIVATED
Running Status: STOPPED
Fetch handler existence: EXISTS
Script: https://drive.google.com/drive/serviceworker.js?ouid=u7d65efeba9d1fc2d
Version ID: 5
Renderer process ID: 0
Renderer thread ID: -1
DevTools agent route ID: -2
Log:

 
Scope: https://drive.google.com/
Registration ID: 2
Navigation preload enabled: false
Navigation preload header length: 0
Active worker:
Installation Status: ACTIVATED
Running Status: STOPPED
Fetch handler existence: EXISTS
Script: https://drive.google.com/drive/serviceworker_root.js?ouid=u7d65efeba9d1fc2d
Version ID: 4
Renderer process ID: 0
Renderer thread ID: -1
DevTools agent route ID: -2
Log:

 
Scope: https://www.google.co.kr/_/chrome/
Registration ID: 0
Navigation preload enabled: false
Navigation preload header length: 4
Active worker:
Installation Status: ACTIVATED
Running Status: RUNNING
Fetch handler existence: EXISTS
Script: https://www.google.co.kr/_/chrome/newtab-serviceworker.js
Version ID: 3
Renderer process ID: 3169
Renderer thread ID: 14
DevTools agent route ID: 3
Log:

 
 
 
 
 
 
After refesh
ServiceWorker
Registrations in: /home/chronos/u-15bf8a0d86582a81e23d662502611702dc803da0 (3)
Scope: https://drive.google.com/drive
Registration ID: 1
Navigation preload enabled: false
Navigation preload header length: 0
Active worker:
Installation Status: ACTIVATED
Running Status: STOPPED
Fetch handler existence: EXISTS
Script: https://drive.google.com/drive/serviceworker.js?ouid=u7d65efeba9d1fc2d
Version ID: 5
Renderer process ID: 0
Renderer thread ID: -1
DevTools agent route ID: -2
Log:

 
Scope: https://drive.google.com/
Registration ID: 2
Navigation preload enabled: false
Navigation preload header length: 0
Active worker:
Installation Status: ACTIVATED
Running Status: STOPPED
Fetch handler existence: EXISTS
Script: https://drive.google.com/drive/serviceworker_root.js?ouid=u7d65efeba9d1fc2d
Version ID: 4
Renderer process ID: 0
Renderer thread ID: -1
DevTools agent route ID: -2
Log:

 
Scope: https://www.google.co.kr/_/chrome/
Registration ID: 0
Navigation preload enabled: false
Navigation preload header length: 0
Active worker:
Installation Status: ACTIVATED
Running Status: STOPPED
Fetch handler existence: EXISTS
Script: https://www.google.co.kr/_/chrome/newtab-serviceworker.js
Version ID: 3
Renderer process ID: 0
Renderer thread ID: -1
DevTools agent route ID: -2
Log:


Comment 7 by bashi@chromium.org, Apr 16 2018

Cc: falken@chromium.org
Thank you for the response. Looks like SW wasn't involved in this situation. Cc-ing falken@ to confirm.

Comment 8 by falken@chromium.org, Apr 16 2018

Labels: -Type-Bug Needs-Investigation Type-Bug-Regression
I don't think we can conclude that yet.

Can testing team or someone else with Chrome OS 66 Beta repro this? My Chromebook is supposedly on Beta but it's version 65. Another Chromebook is stuck on Stable because "This setting is enforced by your administrator."

Labeling this a regression per comment 3.

Comment 9 by falken@chromium.org, May 11 2018

Cc: yawano@chromium.org
+yawano: do you have ideas how to repro/debug this?

Although I guess I'm probably on Chrome Stable 66 now.
Cc: yamaguchi@chromium.org fukino@chromium.org
Chrome OS Files app is simply opening the URL. I don't think there is much Chrome OS specific thing here.
Labels: Needs-Feedback
I'm able to open offline docs without reloading in Chrome 67 Beta.
NextAction: 2018-07-15
Status: WontFix (was: Unconfirmed)
I could not reproduce this, so WontFixing. Reopen if you still see it.

Sign in to add a comment