Re: [w3c/IndexedDB] Implementation report (#213)

Thanks, @ylafon ! I filed a PR with the updated results:

https://github.com/w3c/test-results/pull/121

Here's the "less than 2":

https://rawgit.com/inexorabletash/test-results/idb2/IndexedDB/less-than-2.html

* /IndexedDB/clone-before-keypath-eval.html - edge cases discovered during rework of algorithms
* /IndexedDB/error-attributes.html - we agree to drop DOMError from the platform
* /IndexedDB/idb-binary-key-detached.htm - maybe detaching is not a thing any more?
* /IndexedDB/idbobjectstore_createIndex15-autoincrement.htm - a super awesome edge case discovered by the nodejs implementation
* /IndexedDB/keypath-exceptions.htm - edge cases discovered during rework of algorithms
* /IndexedDB/keypath-special-identifiers.htm - functionality mentioned explicitly in v1 but untested; this is interesting as it requires a special case in the spec
* /IndexedDB/transaction-deactivation-timing.html - inconsistencies discovered while integrating with HTML
* /IndexedDB/upgrade-transaction-lifecycle-user-aborted.html  - edge cases discovered during rework of algorithms

Caveat: Safari apparently has a nasty bug triggered by the /IndexedDB/keypath-exceptions.htm test. (cc: @beidson) Any IDB test run after that times out until the browser is restarted! So any all of the Safari results following that one are invalid. See:
https://rawgit.com/inexorabletash/test-results/idb2/IndexedDB/all.html



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/213#issuecomment-330959340