Closed
Bug 1421808
Opened 7 years ago
Closed 7 years ago
Document treatment of different types in storageArea.set
Categories
(Developer Documentation Graveyard :: Add-ons, enhancement)
Developer Documentation Graveyard
Add-ons
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wbamberg, Unassigned)
Details
Attachments
(1 file)
6.52 KB,
application/x-xpinstall
|
Details |
This is split from bug 1416331, comment 1.
Reporter | ||
Comment 1•7 years ago
|
||
I've tried testing all the types mentioned in https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/storage/StorageArea/set#Parameters. I've attached the extension I used to do this.
Here's what I am seeing:
Type | Firefox | Chrome
-------------------------------------------------------------------------------
String restores restores
Date restores as a string restores as an empty object
Set restores as an empty object restores as an empty object
RegExp restores as an empty object restores as an empty object
Array restores restores
ArrayBuffer restores as an empty object error in set()
TypedArray restores as an array-like object error in set()
Function error in set() restores as an empty object
Does that all look like what you would expect? Note that some of this is contrary to the Chrome docs, too.
Flags: needinfo?(aswan)
Reporter | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
That seems right but redirect to Kris who wrote the actual code in question I believe
Flags: needinfo?(aswan) → needinfo?(kmaglione+bmo)
Reporter | ||
Comment 4•7 years ago
|
||
I've updated the page: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/storage/StorageArea/set.
Reporter | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Flags: needinfo?(kmaglione+bmo)
You need to log in
before you can comment on or make changes to this bug.
Description
•