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

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2016
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Sign in to add a comment

Issue 175063: applicationCache abort method doesn't work correclty

Reported by, Feb 8 2013

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17

Steps to reproduce the problem:
1. Create a simple HTML page using application Cache
2. let the application Cache start to download the entries in the manifest
3. try to write in the console javascript "applicationCache.abort()"; the download won't be interrupted

What is the expected behavior?
As described from the download process should be interrupted.

What went wrong?
"applicationCache.abort()" doensn't interrupt the cache downloading process.

Did this work before? N/A 

Chrome version: 24.0.1312.57  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)

Comment 1 by, Apr 10 2013


Comment 2 by, Aug 25 2015

Status: Archived
Archiving unconfirmed issues, which have not been modified (commented on, updated, etc...) in over 2 years.

Comment 3 by, Sep 17 2015

This is quite bad, that you cannot avoid checking manifest with each and every request when application is already loaded and e.g. ask user if he wants to download new version if the manifest was changed. This also means +1 request for every page that is requested from server. This slows down especially on mobile networks... 

window.applicationCache.addEventListener('checking', function(event) {
}, false);

In safari works fine. Please fix this.. Thank you

Comment 4 by, Sep 17 2015

Labels: -OS-Windows OS-All Cr-Blink-Storage-AppCache Hotlist-Interop
Status: Available

Comment 5 by, Sep 17 2016

Project Member
Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

For more details visit - Your friendly Sheriffbot

Comment 6 by, Sep 19 2016

Owner: ----
Status: WontFix (was: Untriaged)
appcache is deprecated [1, 2], and this issue only impacts perf (not correctness), so it doesn't seem like it's worth trying to fix it.


Sign in to add a comment