On Monday, November 18, 2013 at 1:38 PM, Anne van Kesteren wrote:
> > My next plan here is to attack the hosted apps and get those
> > standardized. This is going much better and I hope that we can have a
> > spec draft for the bookmark-to-homepage use case in just a couple of
> > weeks. I've talked with multiple mobile browser vendors and there is a
> > lot of interest here (I don't want to speak for others which is why
> > I'm avoiding names).
>
>
>
> I think there's still a large problem with these applications. That
> we're not giving them the same cache context as they would have inside
> the browser. That makes a lot of things that are normal interactions
> on the web today, a lot harder to implement.
Can you please provide a few more details and use cases. Or file bugs:
https://github.com/w3c/manifest/issues
> If we want to offer a no
> shared cache feature, it should be opt-in by the application I think.
That might be good. Different runtimes handle this differently (e.g., Chrome
beta on Android shares everything with the browser, while apps added to the
home screen on iOS don’t share anything).
> I think anything that deviates from the current browser security model
> through some kind of end-user UI is not good.
Not sure what you mean here? Which UI are you talking about?
> Bookmarking Gmail should
> not affect the interaction model. We should move towards making the
> browser the OS. Inventing new security models around URLs won't get us
> there.
I generally agree with what you are saying above.
--
Marcos Caceres
_______________________________________________
dev-webapps mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-webapps
