On 6/18/14 8:25 AM, Jonas Sicking wrote:
Another thing that will likely force us to use certified apps for now
is Web Components. We are only enabling those for certified apps for
now since we want to have freedom to make changes to the spec and the
implementation without worrying about breaking other apps or webpages.
Can the email app work without Web Components?
Either way, I definitely agree that, we should certainly look at
reducing those 150ms. But do people really feel comfortable with
making that the only plan? Can we make that happen for Gecko 34
(September 1st)? At what point do we start working on a backup plan
such as the ones discussed in this thread?
So this is the heart of the matter (at least for email/gaia apps and the
idea of "privileged"):
"certified" is being used as an implementation pref switch. There will
always be new things we will want to try, and it helps if Gecko has a
well-constrained set of web apps to try it out, to work out any issues
in the Gecko implementation, maybe help give early feedback on specs. We
need a controlled space that also gets some real world use, but where we
can hopefully update as the Gecko implementation changes.
I am particularly interested in service workers because I am hopeful it
will eliminate the need for email's cookie cache that is used for fast
startup. I expect that will also only be enabled for "certified" apps in
the beginning.
This comes at a cost: Gaia apps will not be able to do installs/updates
via the Marketplace, which also makes it hard to use them on Android via
the web runtime, but the hope is that by having this early testing we
have better APIs and implementations for the web platform in the long run.
So, I think we just need to set the expectation for at least another
year or two, that the gaia set of apps will not be able to be
"privileged", because we need them as early beta testers for features
and capabilities we are building out for the mobile web platform.
In the short term this creates a bit of an issue for email. The
"privileged" setting helped with the new CSP policy desires (bug
1012652) but since email is part of gaia, and email uses some of the
shared resources, I filed bug 1027185 to switch email back to
"certified", and we'll have to use another approach for bug 1012652. I
will confirm the cause of the slowdown for bug 1024005 before switching
email back to certified.
That should end the "privileged" diversion for this thread.
James
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
