Open Bug 787843 Opened 12 years ago Updated 2 years ago

applicationCache.update() throws SecurityError instead of InvalidStateError when cache is not primed

Categories

(Core :: DOM: Core & HTML, defect, P5)

17 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: mail, Unassigned)

Details

(Keywords: html5)

fx 17.0a2 (2012-09-02)

Calling applicationCache.update() throws a SecurityError instead of InvalidStateError when the cache is not primed.

http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html#dom-appcache-update
"If there is no such application cache, or if its application cache group is marked as obsolete, then the method must throw an InvalidStateError exception instead."

The currently thrown error is quite misleading for developers.

Speaking of which: Developers who want to call applicationCache.update should first check that applicationCache.status !== 0 (uncached).
Keywords: html5
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.