e aligning with Firefox is the best path forward here, although
I don't feel strongly.
I still think it's reasonable to do all this as a web-facing PSA instead of a
full Intent to Ship, by the way.
On Fri, Sep 20, 2024 at 2:37 AM 'Abhishek Shanthkumar' via blink-dev
mail
h they have not previously written to it, whereas
"UnknownError" is used in cases where something goes wrong with underlying
storage. So maybe aligning with Firefox is the best path forward here, although
I don't feel strongly.
I still think it's reasonable to do all this as
something goes wrong with underlying
storage. So maybe aligning with Firefox is the best path forward here, although
I don't feel strongly.
I still think it's reasonable to do all this as a web-facing PSA instead of a
full Intent to Ship, by the way.
On Fri, Sep 20, 2024 at 2:37 AM '
Hi, Mike!
The DOMException.name was "DataError" for all cases before this change. It
remains the same for the "recoverable" cases even after this change. I'll add
this to the Summary, thanks!
This error is unique to Chromium because, yes, LevelDB is not used by other
browsers.
Thanks,
Abhis
A correction about the behavior of other browsers - it looks like Firefox too
stores blobs and large values in files separate from the SQLite database.
Deleting the files and then attempting to read the value raises a DOMException
on the IDBRequest with these parameters:
name: "UnknownError"
mess
f error, my read is that although the section at
https://w3c.github.io/IndexedDB/#exceptions implies "NotFoundError" is a good
choice, looking at actual usage in the spec, "NotFoundError" seems to be more
about deterministic cases where the web developer is requesting something from
