- From: Jonas Sicking <jonas@sicking.cc>
- Date: Mon, 2 Dec 2013 21:01:25 -0800
- To: Marcos Caceres <w3c@marcosc.com>
- Cc: Webapps WG <public-webapps@w3.org>, Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>, "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, Web and Mobile IG <public-web-mobile@w3.org>
On Tue, Nov 26, 2013 at 1:02 PM, Marcos Caceres <w3c@marcosc.com> wrote:
> The Editors would appreciate if people take a look and see if you agree with the feature set.
When we did outside-of-browser-UI web apps for FirefoxOS we quickly
found that a lot of developers want to be able to rely on UA-provided
UI such as the back button.
Yes, the app can detect that it's running "standalone" and display a
back button itself. However that was significantly more work than any
other part of creating a "standalone" app, which mostly consisted in
writing a manifest. It's especially a lot of work if you want to try
to replicate the platform-rendered back button on all platforms.
What I think we should have is something like:
"chrome": {
"back": true
}
If the UA doesn't support any of the properties in the "chrome"
section, then the UA should be required to not launch the app in
standalone mode.
I also think that we need a way to put the manifest in-line in the
main document. In part, technologies tend to be a lot easier to
understand if you can create a single-file demo. In part, for small
simple apps, having to separate the manifest into a separate file
could be annoying and might drive people to stick to the existing
meta-tags.
I also think the "dont-share-cookies-and-stuff" thing needs more work
before it's ready for inclusion. So might be better to drop that for
FPWD. But I'm fine with keeping it in for now too and dropping it if
we can't solidify it.
/ Jonas
Received on Tuesday, 3 December 2013 05:02:23 UTC