Safari 15 IndexedDB Leaks

This I can actually answer :D

Multiple reasons:

* No two SQL implementations have the same dialect

* There is no publicly available specification

* The people in charge of the non-free specification have demonstrated no desire to:

    * Make the spec public and freely available

    * Remove (or make mandatory) any optional features

    * Update the spec to match the real world, unify discrepancies, and require conformance to that spec

  * Following the above, existing commercial vendors have no desire to create a unified specification that covers, presumably as that would ease transition between DBs?

The core problem was that existing websql implementations were just shipping wrappers around sqlite. That meant no one could create an implementation without first doing a blackbox rewrite of sqlite, and would just have to hope they hadn't messed up anywhere.

It looks like the page only does a User-Agent check[1]. The sites under "The demo detects the following websites:" is just a list of sites that the demo has hardcoded support for detecting[2].

[1] https://github.com/fingerprintjs/blog-indexeddb-safari-leaks...

[2] https://github.com/fingerprintjs/blog-indexeddb-safari-leaks...

It is reporting "not affected" for me on Firefox stable and nightly. It does show a list of domains at the bottom that it would check if the brower was exploitable.

How so?