Closed Bug 729777 (aboutPagesDOMStorage) Opened 14 years ago Closed 13 years ago

Eradicate localStorage from about: pages

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 25

People

(Reporter: khuey, Assigned: mak)

References

(Blocks 1 open bug)

Details

(Keywords: meta, Whiteboard: [Snappy:P1])

No description provided.
I'm told there may already be bugs for this.
I suppose I could be a jerk an INCOMPLETE this for lack of context, but I'll instead ask for some! :) [If for no other reason than people not following IRC on a daily basis will wonder what's up.]
localStorage is a Web platform API that will be around for years to come... unless we want to break the Web. Context for this bug would be appreciated.
basically the request is to not use localStorage in about pages (about:home and about:newTab), cause it has a cost.
Summary: Eradicate localStorage from the browser frontend → Eradicate localStorage from about: pages
I suppose a the suggested replacement is indexedDB, that does all IO on a separate thread.
(In reply to Marco Bonardo [:mak] from comment #5) > I suppose a the suggested replacement is indexedDB, that does all IO on a > separate thread. Probably.
(In reply to Marco Bonardo [:mak] from comment #4) > basically the request is to not use localStorage in about pages (about:home > and about:newTab), cause it has a cost. Sure, doing this reduces a couple of pages that use localStorage. IMO our efforts would be better spent reducing the performance cost of localStorage for Firefox users who experience that cost every day whether our about: pages use it or not.
(In reply to Dietrich Ayala (:dietrich) from comment #7) > (In reply to Marco Bonardo [:mak] from comment #4) > > basically the request is to not use localStorage in about pages (about:home > > and about:newTab), cause it has a cost. > > Sure, doing this reduces a couple of pages that use localStorage. > > IMO our efforts would be better spent reducing the performance cost of > localStorage for Firefox users who experience that cost every day whether > our about: pages use it or not. Somebody is going to have to pay the cost of synchronously accessing the disk. Right now it's the whole browser. Taras and I have a plan to make it so that only the relevant page pays that cost, but if the pages the browser runs on startup are using localStorage ...
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #8) > but if the pages the browser > runs on startup are using localStorage ... IIRC, the grand plan from UX is to turn on session restore by default at some point.
Another option is to mount a project-wide assault on the use of global/local/sessionStorage, because it's broken by design: * encourage standards bodies to deprecate early * make the MDN docs scary as hell * make the MDN docs for IndexedDB awesome as hell * create a social media armageddon around how bad it is
(In reply to Dietrich Ayala (:dietrich) from comment #10) > * create a social media armageddon around how bad it is well, we just blogged about how awesome it is, like 2 days ago.
Depends on: 749477
Whiteboard: [Snappy:P1]
Depends on: 789348
Depends on: 790178
Keywords: meta
Assignee: nobody → mak77
Status: NEW → ASSIGNED
Blocks: 889442
No longer blocks: 889442
Depends on: 889442
Blocks: StorageJank
Alias: aboutPagesDOMStorage
I think this is fixed, with bug 889442 changed to be blocked by this one (that dependency got flipped).
(In reply to Florian Bender from comment #12) > (that dependency got flipped). for good reasons, I don't consider this fixed until we stop allowing to misuse dom storage.
Fixed by dependencies, finally.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 25
You need to log in before you can comment on or make changes to this bug.