This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21418 - I'm working on html5 apps which need to have offline work capability and am using localstorage. But we have a huge challenge of supporting multiple browsers. Localstorage specification does not sp [...]
Summary: I'm working on html5 apps which need to have offline work capability and am u...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: All other
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-28 06:20 UTC by contributor
Modified: 2013-03-28 21:55 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2013-03-28 06:20:12 UTC 
Specification: http://dev.w3.org/html5/webstorage/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
I'm working on html5 apps which need to have offline work capability and am
using localstorage. But we have a huge challenge of supporting multiple
browsers. 

Localstorage specification does not specify that this should work across the
browsers. For example if I load the html5 page in firefox and store something
in localcache, I cannot retrieve it if I open the same page in IE. This will
result in multiple instances of cache and for a offline application it could
lead to huge sync issues. 

Technologies like flash or silverlight handled this well. While each browser
might implement this differently, there should be some common storage/service
at the OS level to ensure there is only one store.

I want to suggest that this will be a very good feature to add in the spec. 
Please let me know how to propose this feature.

Seshu KUmar Adiraju
seshukumar_adiraju@infosys.com

Posted from: 115.248.154.196
User agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MS-RTC EA 2; .NET4.0C; .NET4.0E; MS-RTC LM 8; .NET CLR 1.1.4322; InfoPath.3)
Comment 1 Ian 'Hixie' Hickson 2013-03-28 21:55:37 UTC 
You should handle different browsers on the same machine the same way you would handle different user profiles in Chrome or Firefox, or different laptops for the same user, or a phone and a desktop for the same user, or the localStorage of a browser after the user has cleared it, or after they got a new computer because they dropped their previous one in a river accidentally.