t;> > Spitzer
>> > Sent: Monday, June 8, 2015 21:10
>> > To: wha...@whatwg.org
>> > Subject: [whatwg] Persistent state for homescreen web apps (without
>> > reloading each time)
>> >
>> > Is it within the scope of the spec to specify w
> On Jun 9, 2015, at 3:55 PM, Zac Spitzer 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
that.
-Original Message-
From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Zac
Spitzer
Sent: Monday, June 8, 2015 21:10
To: wha...@whatwg.org
Subject: [whatwg] Persistent state for homescreen web apps (without
reloading each time)
Is it within the scope
On Mon, Jun 8, 2015 at 8:10 PM, Zac Spitzer zac.spit...@gmail.com wrote:
Is it within the scope of the spec to specify whether home screen web apps
should
retain their loaded state when switching from foreground to background and
back to foreground again?
Chrome behaves exactly as expected,
Of Zac
Spitzer
Sent: Monday, June 8, 2015 21:10
To: wha...@whatwg.org
Subject: [whatwg] Persistent state for homescreen web apps (without
reloading each time)
Is it within the scope of the spec to specify whether home screen web
apps
should retain their loaded state when switching
Is it within the scope of the spec to specify whether home screen web apps
should
retain their loaded state when switching from foreground to background and
back to foreground again?
Chrome behaves exactly as expected, however, iOS reloads the web app each
time