This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27727 - Remove DOMError from IDB
Summary: Remove DOMError from IDB
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-02 22:40 UTC by Ms2ger
Modified: 2015-05-21 23:26 UTC (History)
4 users (show)

See Also:

Attachments

Description Ms2ger 2015-01-02 22:40:56 UTC 
See bug 21740.
Comment 1 Joshua Bell 2015-01-07 19:04:35 UTC 
Tentatively resolving as "LATER" as we'd do this in a follow-up version of the spec (e.g. "IDB v2"), but I'll let others wrangle W3C process and inter-spec reference requirements.

(And yeah, would be nice to eliminate DOMError, but it's shipping in browsers now so like eliminating DOMStringList I'm not sure it'll be as easy as dom.spec.whatwg.org implies. At least it has no methods.)
Comment 2 Joshua Bell 2015-01-12 17:34:08 UTC 
Just to clarify - we were marking everything that wasn't aimed at "v1" as RESOLVED / LATER per https://www.w3.org/2008/webapps/wiki/IndexedDatabaseFeatures - which is why I resolved this issue. (And added a note to that page about it.)

But now that "v1" is out the door, we can start tackling these in "v2". So I'm okay with re-opening. Once the "second edition" spec is in a canonical location (I have it in a personal repo at the moment) we can re-open the lot of 'em and start crossing off the easy* bugs like this one.

* At least until we get implementer feedback about feasibility. :)
Comment 3 Joshua Bell 2015-05-21 23:26:08 UTC 
Now tracked as: https://github.com/w3c/IndexedDB/issues/16