On Thu, Dec 14, 2017 at 11:11 AM, Bevis Tseng <bts...@mozilla.com> wrote: > On Thu, Dec 14, 2017 at 12:05 PM L. David Baron <dba...@dbaron.org> wrote: > >> >> Given that we implement the specification as described in: >> https://hacks.mozilla.org/2016/10/whats-new-in-indexeddb-2-0/ >> and that Bevis (who implemented it) agrees, I intend to vote in >> favor. >> > These are small improvement of existing IndexedDB APIs wanted by web > developers and are shipped since FF51, so I agree to vote it as proposed > recommendation.
Thanks Bevis, and agreed, we should vote to support this implementation. I just have a few questions (maybe worth adding as comments). See below. In diving into the implementation report: https://wpt.fyi/IndexedDB It looks like nearly everything has 2+ interop implementations. There are about a dozen test rows that *only* pass in Chrome, which is a bit concerning. There is one test row that is red for all implementations, digging into it. https://wpt.fyi/IndexedDB/idbobjectstore_createIndex15-autoincrement.htm It looks like there are problems with "Auto-Increment Primary Key", specifically: * Chrome & Edge fail the test * FF & Safari - we don't have results (not sure what just "ERROR" means) So two things. 1. For us (Firefox platform) - do we have bugs filed for the tests we are failing? 2. For the WG: Is there an explanation for why the spec exited CR with ~ a dozen tests (or test rows) only having a single passing implementation (Chrome) ? Thanks, Tantek _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
