Closed Bug 983882 Opened 11 years ago Closed 9 years ago

Give feedback in the console about appcache status

Categories

(DevTools :: Console, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: cvan, Unassigned)

Details

1. Load Chrome 2. With a clear appcache, load http://developers.whatwg.org/ 3. Inspect the console: Creating Application Cache with manifest http://developers.whatwg.org/offline.manifest developers.whatwg.org/:1 Application Cache Checking event developers.whatwg.org/:1 Application Cache Downloading event developers.whatwg.org/:1 Application Cache Progress event (0 of 70) http://developers.whatwg.org/browsers.html developers.whatwg.org/:1 Application Cache Progress event (1 of 70) http://developers.whatwg.org/tabular-data.html developers.whatwg.org/:1 Failed to load resource: the server responded with a status of 404 (Not Found) http://developers.whatwg.org/link-fixup.js Application Cache Progress event (2 of 70) http://developers.whatwg.org/the-map-element.html developers.whatwg.org/:1 ... Application Cache Progress event (70 of 70) developers.whatwg.org/:1 Application Cache Cached event 3. Refresh the page 4. Inspect the console: Document was loaded from Application Cache with manifest http://developers.whatwg.org/offline.manifest developers.whatwg.org/:1 Application Cache Checking event developers.whatwg.org/:1 Application Cache NoUpdate event (index):1 The Firefox Developer Tools console should provide similar feedback.
With Service Worker debugging in progress and app cache being deprecated (https://html.spec.whatwg.org/multipage/browsers.html#offline) we aren't going to add additional app cache logging. If someone did want to do it, they could instrument the platform with calls to ReportToConsole for the relevant progress events: https://dxr.mozilla.org/mozilla-central/rev/be593a64d7c6a826260514fe758ef32a6ee580f7/dom/base/nsContentUtils.cpp#3438
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.