If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

The Web API incorrectly implies the domain is the ultimate ancestor/owner of stored content

UNCONFIRMED
Unassigned

Status

Developer Documentation
API: Miscellaneous
P5
normal
UNCONFIRMED
9 months ago
9 months ago

People

(Reporter: Codacoder, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

9 months ago
:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: 

:: Details

The page begins with: 

  The Web Storage API provides mechanisms by which browsers can store key/value pairs, in a much more intuitive fashion than using cookies.

And goes on to talk as if "web storage" is accessible via specific keys under a specific domain. That's misleading in two ways:

1 - It's not "web" storage, it's UA specific. (I realize mozilla are not responsible for the w3c's naming choices but...)

2 - The phrasing "browsers can" doesn't make clear that Firefox, for example, cannot access localStorage created via Chrome, for example.

Somewhere it should be made clear that "web" in this context doesn't mean anything like it does anywhere else in web tech. Also, make clear that localStorage is keyed *first* to the current UA, THEN the domain.

In short, WS is NOT browser-agnostic and the text should make that clear.
(Reporter)

Comment 1

9 months ago
I definitely added this to the initial report but it didn't show up?

https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API
You need to log in before you can comment on or make changes to this bug.