Can anyone tell me what the limits are for local storage in an HTML5 browser game, and how this varies across browsers? I've seen how advanced games and other projects can be using WebGL and advanced JS pre-compilers these days but data/assets appears a big bottleneck. Let's assume a 100Mbps internet connection (very optimistic) - this means we could download 1Gb of assets in about 2 minutes, which is already a pretty long wait-time before those assets are processed and you can start. Every time you re-load this site, you have to do it again.
So do Chrome and others (but I'm assuming Chrome is the most advanced) provide a way for storing more than a few Mb between sessions? I understand sandboxing and security mean this is very locked down but are there any workarounds to get local file access suitable for large assets?
I'm assuming compression of assets is already done, and that procedural generation is not feasible, in this question - once everything else is done we still have 1GB+ of data we need.