- From: Ryosuke Niwa <rniwa@apple.com>
- Date: Fri, 09 Oct 2015 12:02:45 -0700
- To: Zac Spitzer <zac.spitzer@gmail.com>
- Cc: whatwg@whatwg.org, Domenic Denicola <d@domenic.me>
> On Jun 9, 2015, at 3:55 PM, Zac Spitzer <zac.spitzer@gmail.com> wrote: > > But what do end users or developers expect in terms of browser behavior in > this situation? > > The history api (or saving state to indexedDB) aren't going to solve the > problem of reinitialization everytime the user switches back to a web app. > Users expect them to behave like a native app. That seems like a very platform/product specific issue to me. I don't think we want W3C to be mandating how Web browsers should interact with the rest of the system. > Chrome handles this as users and developers expect, web apps get paged out > and require a reload depending on memory etc. Safari does it every single > time By Chrome, do you mean Android? Again, this is really about the platform-dependent behavior we shouldn't be spec'ing in W3C. Please file a new bug on our bug tracker at http://radar.apple.com - R. Niwa
Received on Friday, 9 October 2015 19:03:17 UTC