| I commented about this in a different thread about the same topic earlier today, but I'll post here as well. I can understand Apple's decision to do this, as there's a lot that can be improved about offline storage on the web: * asking for user permission (i've seen demos try to exhaust the users' storage, and trackers can use this to invade privacy)
* async writes and reads However, making a change like this with no suitable alternative leaves PWA developers stuck in a hard place. I'm not sure what can be done in the short term here. There's a few web specs that address these issues. I'd love to see them come further along, and maybe improve things for developers and users in the long run. If anyone knows, is there anything that members of the community can do to support these efforts? https://chromestatus.com/feature/6428344899862528 https://wicg.github.io/kv-storage/ https://chromestatus.com/feature/5715811364765696 https://storage.spec.whatwg.org/ |