27727 2015-01-02 22:40:56 +0000 Remove DOMError from IDB 2015-05-21 23:26:08 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified All All RESOLVED MOVED P2 normal --- 1 Ms2ger dave.null art.barstow jsbell mike public-webapps public-webapps-bugzilla oldest_to_newest 116730 0 Ms2ger 2015-01-02 22:40:56 +0000 See bug 21740. 116895 1 jsbell 2015-01-07 19:04:35 +0000 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.) 117024 2 jsbell 2015-01-12 17:34:08 +0000 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. :) 120408 3 jsbell 2015-05-21 23:26:08 +0000 Now tracked as: https://github.com/w3c/IndexedDB/issues/16