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

@inexorabletash superb!

We usually only put the results of the latest version into the [implementation report](https://w3c.github.io/test-results/IndexedDB/), but it doesn't hurt to keep the `.json` files in the repo as historical records.

I'm hoping we can move to PR with error-attributes.html as an exception... unless we find any missing test, I'll send out the transition request this week.

Btw, do you plan to continue the [editing of IndexedDB ](https://w3c.github.io/IndexedDB/) after 2.0 exits CR? We are using a script to auto-generate the `.html` doc from `.bs` files and push it to gh-pages for the specs using Bikeshed these days, see the [IntersectionObserver repo](https://github.com/w3c/IntersectionObserver/commit/aa99f06dc908861c59a3ad256fbb36fe686e178a) as an example. Would you like us to set up this workflow in the IndexedDB repo too?

-- 
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-331865344