Issue metadata
Sign in to add a comment
|
Application Cache serving SharedWorker resources |
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
Steps to reproduce the problem:
1. Close all SharedWorkers in chrome://inspect#workers
2. Navigate to a page that has an AppCache manifest with JS resources (e.g. "/foo.js") on the same domain and wait for AppCache to sync
3. Go offline
4. Navigate to the manifest by URL, it should be loaded from AppCache
5. Bring up the developer console, and enter:
new SharedWorker("/foo.js");
6. Go to chrome://inspect#workers - the SharedWorker is not created
7. Navigate to the javascript resource by URL, it should loaded from AppCache
What is the expected behavior?
The SharedWorker's script should be accessible given that it is in the Application Cache and being requested from the same domain.
What went wrong?
The SharedWorker failed to load the javascript resource
Did this work before? Yes 51.0.2704 and prior on Linux
Chrome version: 52.0.2743.116 Channel: stable
OS Version:
Flash Version: Shockwave Flash 22.0 r0
Working as intended on Chrome 52.0.2743.116 on OSX 10.11.6. Haven't tested on other platforms.
,
Aug 8 2016
,
Aug 10 2016
edisont@, do you have any handy example to confirm? nhiroki@, I assign this issue to you for now. Could you take a look (and pass this to another person for implementation)?
,
Aug 10 2016
,
Aug 10 2016
michaeln@, can you triage this?
,
Aug 11 2016
Does the site also use a serviceworker? Appcache tries to get out of the way if serviceworkers are involved.
,
Aug 12 2016
Ah ha, the site does use serviceworkers. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Aug 6 2016