BCCing public-webapps@, as this proposal started there[1]. It looks like it
might be reasonable to charter the spec work as part of the WebAppSec
WG[2], however, so I'm moving the conversation here for the time being.
Way back in August, I proposed a credential management API. After some
On Thu, Oct 16, 2014 at 5:22 PM, Shijun Sun shij...@microsoft.com wrote:
This is very helpful. I assume the browser running the service worker can
be a very light-weight version (or a subset of the full browser) since we
don't need to render an actual webpage. Is that the right expectation?
On Thursday, October 16, 2014 8:29 AM, Anne van Kesteren wrote
On Thu, Oct 16, 2014 at 5:22 PM, Shijun Sun shij...@microsoft.com wrote:
(1) the Push Client displays a notification right away, the user chooses
to pick up the call or dismiss, the browser launch with the app based on
user
On 16 October 2014 08:55, Shijun Sun shij...@microsoft.com wrote:
Re #2, it'd be great if some folks could comment on the scheduling and
latency question.
There are number of variations on how this all works out. And
multiple sources of latency.
A mobile device in a low power state follows a
On 16 October 2014 16:22, Shijun Sun shij...@microsoft.com wrote:
On Thursday, October 16, 2014 12:42 AM, Anne van Kesteren wrote:
You need a browser to run a service worker. The browser is pinged and it
might then decide to start running a service worker to process the incoming
message, or
On 16 October 2014 11:17, John Mellor joh...@google.com wrote:
In our prototype on Android, it takes less than a second (not yet optimized)
to wake up Chrome from a cold start and handle the event in a Service Worker
(the demo writes to IndexedDB and shows a notification), versus less than
On Thursday, October 16, 2014 11:46 AM, Martin Thomson wrote
If the push message is being used to deliver a call notification, that sort
of delay will definitely be noticed. And I'm assuming that you've tested on
a high end Nexus or something like that. Add the latencies involved in
Is it legal to register a type extension on top of an existing custom tag?
x-button is=x-submit-button/x-button
var ButtonPrototype = Object.create(HTMLElement.prototype)
document.registerElement(x-button, {prototype: ButtonPrototype})
var SubmitButtonPrototype =
Hi Joshua,
I implemented Custom Elements in Chrome.
In the definition construction algorithm
http://www.w3.org/TR/custom-elements/#dfn-definition-construction-algorithm,
step 8.2, it says:
If BASE does not exist or is an interface for a custom element, set ERROR
to InvalidName and stop.
In
