26492 2014-07-31 23:45:19 +0000 IndexedDB: add/put/update operations should define ordering of clone vs. keypath evaluation 2015-05-19 22:15:03 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC Linux RESOLVED FIXED P2 normal --- 1 jsbell dave.null jonas me mike public-webapps public-webapps-bugzilla oldest_to_newest 109726 0 jsbell 2014-07-31 23:45:19 +0000 We recently fixed a bug in Chromium, but it looks like it affects Firefox as well and is implicit in the web-platform-tests suite (key_invalid.htm) var store = db.createObjectStore('store', {keyPath: 'keypath'}); var values = ['string1', 'string2']; var obj = { get keypath() { return values.shift(); } }; store.put(obj); store.openCursor().onsuccess = function(e) { console.log('key is: ' + e.target.result.key); console.log('value has: ' + JSON.stringify(e.target.result.value.keypath)); }; In FF33 the key is 'string1' and the value has 'string2'. Having these out of sync seems like a violation of the intent of the spec, although the letter of the spec does imply tests before cloning. In Chromium (circa 38) we clone, then evaluate the keypaths, so the result is 'string1' / 'string1'. This manifests in the key_invalid.htm test since it provides invalid key values such as function(){}. In Chromium we return DataCloneError since we clone before evaluating, whereas the test looks for DataError since it assumes evaluation before cloning. 109727 1 jonas 2014-08-01 00:26:25 +0000 I agree that the spec should call for first cloning, then evaluating the keypath on the clone. 109782 2 me 2014-08-02 03:21:19 +0000 Yeah we discussed this at Mozilla a year or two ago and came to a similar conclusion. Fixing it hasn't been a priority for us yet though. 120374 3 jsbell 2015-05-19 22:15:03 +0000 This has been "fixed" in the V2 spec, although it may not match reality exactly. https://w3c.github.io/IndexedDB/