Re: [admin] putting Push API in W3C's Github repo [Was: Re: Progress on Push API]

2014-05-01 Thread Mounir Lamouri
On Thu, 1 May 2014, at 21:38, Arthur Barstow wrote: On 4/30/14 1:19 PM, Mounir Lamouri wrote: On Thu, 1 May 2014, at 1:50, EDUARDO FULLEA CARRERA wrote: On 30 abr 2014 at 16:52:49, Arthur Barstow wrote: On 4/30/14 10:44 AM, Arthur Barstow wrote: I'll work with Mike/Robin to create a new

RfC: LCWD of DOM Parsing and Serialization; deadline May 22

2014-05-01 Thread Arthur Barstow
[ Bcc: public-webapps and public-html-admin; please Reply-to: www-dom ] WebApps requests comments on the May 1 Last Call Working Draft of DOM Parsing and Serialization (DOMParser, XMLSerializer, innerHTML, and similar APIs): http://www.w3.org/TR/2014/WD-DOM-Parsing-20140501/ If you have

[webcomponents]: Regular Conference Call Survey

2014-05-01 Thread Dimitri Glazkov
Greetings, WebApp-ateurs! At the last F2F, there was some positive sentiment toward setting up a regular conference call to discuss Web Components-related topics. On Art's advice, I thereby present this lovely survey that seeks to find a good time slot for such a conference call:

Re: [webcomponents]: Regular Conference Call Survey

2014-05-01 Thread Ryosuke Niwa
I guess I wasn't paying attention when this came up during F2F but I probably wouldn't be able to participate in regular conference calls due to time constraints. I'm not, however, opposed to others having such conference calls as long as minutes/summary of discussions are posted on the

Re: [webcomponents]: Regular Conference Call Survey

2014-05-01 Thread Arthur Barstow
On 5/1/14 5:13 PM, Ryosuke Niwa wrote: I'm not, however, opposed to others having such conference calls as long as minutes/summary of discussions are posted on the mailing list. The expectation is the meeting will be announced at least 24 hours in advance and that minutes will be taken in

Re: Progress on Push API

2014-05-01 Thread Jonas Sicking
I'll give it a shot to define an outline here. The problem that we're trying to solve is to let a webpage know when it needs to register for push notifications. This happens either when the page never has registered, or if the push server lost track of the registration that was previously done.

Re: Progress on Push API

2014-05-01 Thread Martin Thomson
On 1 May 2014 16:55, Jonas Sicking jo...@sicking.cc wrote: function registrationHandler() { navigator.push.register().then((endpoint) = { sendBackToAppServer(endpoint); navigator.push.registrationNeeded.then(registrationHandler); } }

contentEditable=minimal

2014-05-01 Thread Ben Peters
I have been discussing a new concept with some people for enabling a subset of contentEditable behavior without all of the built-in formatting and some other functionality. It was discussed a bit at the Extensible Web Summit [1]. Below is a draft I wrote about this, which is also on GitHub [2].

Re: Progress on Push API

2014-05-01 Thread Jonas Sicking
On Thu, May 1, 2014 at 5:26 PM, Martin Thomson martin.thom...@gmail.com wrote: On 1 May 2014 16:55, Jonas Sicking jo...@sicking.cc wrote: function registrationHandler() { navigator.push.register().then((endpoint) = { sendBackToAppServer(endpoint);

Re: Progress on Push API

2014-05-01 Thread Martin Thomson
On 1 May 2014 17:31, Jonas Sicking jo...@sicking.cc wrote: If it's going to happen over and over, why not an event? function register() { navigator.push.register().then(endpoint = sendToAppServer(endpoint)); } navigator.push.onderegister = e = register; For two reasons: * If the page