Closed
Bug 601774
Opened 15 years ago
Closed 15 years ago
IndexedDB: Audit exceptions thrown from indexedDB methods
Categories
(Core :: Storage: IndexedDB, defect)
Core
Storage: IndexedDB
Tracking
()
RESOLVED
FIXED
People
(Reporter: bent.mozilla, Assigned: bent.mozilla)
Details
Attachments
(1 file)
186.36 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
Need to make sure we don't leak implementation details through exceptions, and need to make sure we throw the exception code that the spec suggests.
Assignee | ||
Comment 1•15 years ago
|
||
This fixes all our error codes, I think.
Attachment #485516 -
Flags: review?(jonas)
Comment on attachment 485516 [details] [diff] [review]
Patch, v1
> IDBDatabase::RemoveObjectStore(const nsAString& aName)
...
> if (aName.IsEmpty()) {
>- return NS_ERROR_INVALID_ARG;
>- }
Just remove this part.
I have to say though, I think this patch is a really bad idea. It'll make debugging harder both for us and for authors to clamp all the errors.
The security review comments was only about the security sensitive errors. Feel free to check this with the others who were at the review :)
The only security sensitive errors that I can think of are file handling related ones, and possibly ones related to what particular version of sqlite is installed.
So only return values from sqlite are the ones we should clamp.
I'm fine with doing this for now though.
Attachment #485516 -
Flags: review?(jonas) → review+
blocking2.0: --- → betaN+
Assignee | ||
Comment 3•15 years ago
|
||
Status: ASSIGNED → RESOLVED
blocking2.0: betaN+ → ---
Closed: 15 years ago
Resolution: --- → FIXED
Component: DOM → DOM: IndexedDB
Version: Trunk → unspecified
You need to log in
before you can comment on or make changes to this bug.
Description
•