most (all?) mozilla specific objects in content are prefixed by moz not moz_. So, moz_indexedDB really must be mozIndexedDB.
I agree, but Tantek seems to have other opinion about vendor prefixing https://wiki.mozilla.org/Tantek-Mozilla-projects#DOM_API_vendor_prefixing
standardization of non-standard implementation object names is interesting, but I am not sure what sort of long term value there is. I do value the consistency with all other non-standard object names we have used.
Created attachment 497631 [details] [diff] [review] patch v.1 (core)
Attachment #497631 - Flags: review?(jonas)
Created attachment 497632 [details] [diff] [review] patch v.1 (tests)
pushing to try.
ben, i can update your patch queue, or update m-c after you land.
Created attachment 497883 [details] [diff] [review] patch v.2 (tests)
Attachment #497631 - Flags: review?(jonas) → review+
Attachment #497883 - Flags: review?(jonas) → review+
jst, can you review?
blocking2.0: --- → ?
Attachment #497883 - Flags: approval2.0+
Attachment #497631 - Flags: approval2.0+
blocking2.0: ? → -
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Docs refer to this as mozIndexedDB, so doc complete on this one.
Keywords: dev-doc-needed → dev-doc-complete
Component: DOM → DOM: IndexedDB
You need to log in before you can comment on or make changes to this bug.