On the other hand, for people with a lot of "hard-offline" situations, the ability to "set up" for offline is important, and automatic management works less good for that situation. I think the web needs a "Keep/Install" mode for that situation.
-
-
Replying to @wycats @littlecalculist
That's PWA install + https://developers.google.com/web/fundamentals/instant-and-offline/web-storage/offline-for-pwa …
1 reply 0 retweets 4 likes -
At the limit, eviction still possible, but combined with UI changes, much less likely
1 reply 0 retweets 1 like -
Replying to @slightlylate @littlecalculist
I think this is roughly right for "web apps" (user agent specified limits, not many specified guarantees), but I think you still want something more guaranteed via something that looks like app installs. On balance, this situation is still great though, and best in class!
2 replies 0 retweets 2 likes -
Replying to @wycats @littlecalculist
Persistent Storage is probably what we need to evolve to handle hard cases. I.e., would you trade isolation for real persistence?
1 reply 0 retweets 0 likes -
E.g., requiring a CSP value that opts the app into its own storage partition at all times in order to gain real persistence at install time
1 reply 0 retweets 0 likes -
Replying to @slightlylate @littlecalculist
Would this mean you would have to use the same origin for all content (what about fonts?)
1 reply 0 retweets 0 likes -
Replying to @wycats @littlecalculist
Wouldn't need to be same-origin only, but all cookies, caches, etc. etc. would be effectively double-keyed. E.g.: `Content-Security-Policy: sandbox-storage; ...`
2 replies 0 retweets 1 like -
Replying to @slightlylate @littlecalculist
What would the effect of the double-keying be?
1 reply 0 retweets 0 likes -
Replying to @wycats @littlecalculist
A big one would be that iframes of your origin outside of top-level loads would not include any of the state the user added in top-level navigation contexts.
1 reply 0 retweets 0 likes
I.e., the end of XSRF.
-
-
Replying to @slightlylate @littlecalculist
If it only affects credentialed content, BRING IT FUCKING ON
1 reply 0 retweets 0 likes -
Replying to @wycats @littlecalculist
Would be all content. Why the credentialing difference?
1 reply 0 retweets 0 likes - 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.