Re: Refactoring SharedWorkers out of Web Workers W3C spec

2013-12-11 Thread Simon Pieters
On Tue, 10 Dec 2013 20:14:35 +0100, Travis Leithead travis.leith...@microsoft.com wrote: During TPAC 2013 in Shenzhen, I took an action item [1][2] to remove Shared Workers from the W3C Web Workers spec [3] in order for the spec to pass the first of the two stated CR exit criteria in the

Re: [webcomponents] Standard Use Case (Was Auto-creating shadow DOM for custom elements)

2013-12-11 Thread Matthew McNulty
On Tue, Dec 10, 2013 at 4:04 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 9, 2013, at 9:34 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 9, 2013, at 11:13 AM, Scott Miles sjmi...@google.com wrote: I'm not wont to try to summarize it here, since he said it already better there. Perhaps

Re: Refactoring SharedWorkers out of Web Workers W3C spec

2013-12-11 Thread Simon Pieters
On Tue, 10 Dec 2013 22:09:38 +0100, Jonas Sicking jo...@sicking.cc wrote: We at Mozilla just finished our implementation of Shared Workers. It will be turned on in the nightly releases starting tomorrow (or maybe thursday) and will hit release on April 29th. Excellent. So if we are only

Re: [manifest] HTTP-based solution for loading manifests

2013-12-11 Thread Mounir Lamouri
On Wed, Dec 11, 2013, at 14:48, Marcos Caceres wrote: Would any potential implementer consider supporting a HTTP based solution to loading manifests? It seems quite premature to discuss a HTTP based solution to advertise a manifest. Even if it happens to be something developers ask for, we

Re: [manifest] HTTP-based solution for loading manifests

2013-12-11 Thread Julian Reschke
On 2013-12-11 13:13, Mounir Lamouri wrote: On Wed, Dec 11, 2013, at 14:48, Marcos Caceres wrote: Would any potential implementer consider supporting a HTTP based solution to loading manifests? It seems quite premature to discuss a HTTP based solution to advertise a manifest. Even if it

Re: Refactoring SharedWorkers out of Web Workers W3C spec

2013-12-11 Thread Arthur Barstow
On 12/11/13 6:39 AM, ext Simon Pieters wrote: On Tue, 10 Dec 2013 22:09:38 +0100, Jonas Sicking jo...@sicking.cc wrote: We at Mozilla just finished our implementation of Shared Workers. It will be turned on in the nightly releases starting tomorrow (or maybe thursday) and will hit release on

Re: [manifest] HTTP-based solution for loading manifests

2013-12-11 Thread Marcos Caceres
On Wednesday, December 11, 2013, Julian Reschke wrote: On 2013-12-11 13:13, Mounir Lamouri wrote: On Wed, Dec 11, 2013, at 14:48, Marcos Caceres wrote: Would any potential implementer consider supporting a HTTP based solution to loading manifests? It seems quite premature to discuss a

Re: [manifest] HTTP-based solution for loading manifests

2013-12-11 Thread Julian Reschke
On 2013-12-11 19:59, Marcos Caceres wrote: On Wednesday, December 11, 2013, Julian Reschke wrote: On 2013-12-11 13:13, Mounir Lamouri wrote: On Wed, Dec 11, 2013, at 14:48, Marcos Caceres wrote: Would any potential implementer consider supporting a HTTP

RE: Refactoring SharedWorkers out of Web Workers W3C spec

2013-12-11 Thread Travis Leithead
From: Arthur Barstow [mailto:art.bars...@nokia.com] wrote: Travis - would you please add results for IE? Done. Note: IE's implementation generates a Syntax Error on 'new Worker(#)' which causes a huge chunk of these tests to fail, where otherwise, I think we would be passing them if we could

[custom elements] Improving the name of document.register()

2013-12-11 Thread Edward O'Connor
Hi, The name register is very generic and could mean practically anything. We need to adopt a name for document.register() that makes its purpose clear to authors looking to use custom elements or those reading someone else's code that makes use of custom elements. Here are some ideas:

Re: [custom elements] Improving the name of document.register()

2013-12-11 Thread pira...@gmail.com
I have seen registerProtocolHandler() and it's being discused registerServiceWorker(). I believe registerElementDefinition() or registerCustomElement() could help to keep going on this path. Send from my Samsung Galaxy Note II El 11/12/2013 21:10, Edward O'Connor eocon...@apple.com escribió:

Re: [custom elements] Improving the name of document.register()

2013-12-11 Thread Brian Kardell
On Wed, Dec 11, 2013 at 3:17 PM, pira...@gmail.com pira...@gmail.comwrote: I have seen registerProtocolHandler() and it's being discused registerServiceWorker(). I believe registerElementDefinition() or registerCustomElement() could help to keep going on this path. Since a custom element is

Workers v2 (Was: Refactoring SharedWorkers out of Web Workers W3C spec)

2013-12-11 Thread Ian Hickson
On Tue, 10 Dec 2013, Jonas Sicking wrote: However I'd really like to see us start a level 2 of the spec. The synchronous messaging channels is something else I'd like to see done there. There's seven features I'm aware of that people have asked for that aren't in Workers currently, or are

Re: Workers v2 (Was: Refactoring SharedWorkers out of Web Workers W3C spec)

2013-12-11 Thread pira...@gmail.com
- Canvas in Workers There's been various proposals, including one in the spec that hasn't met with implementor approval; I'm waiting for something to get traction amongst the competing proposals. - Being clearer about what features are visible in workers Blocked on:

Re: Workers v2

2013-12-11 Thread Ian Hickson
On Wed, 11 Dec 2013, pira...@gmail.com wrote: - Canvas in Workers There's been various proposals, including one in the spec that hasn't met with implementor approval; I'm waiting for something to get traction amongst the competing proposals. - Being clearer about what

Re: Workers v2

2013-12-11 Thread pira...@gmail.com
Thanks for the clarification :-) It shouldn't be dificult, specially for DataChannels: WebWorkers has already support for WebSockets and their API is the same (and the security context fairly similar...). I agree on let this discussion to the WebRTC group. Send from my Samsung Galaxy Note II El

Re: Styling form control elements

2013-12-11 Thread Jonas Sicking
On Tue, Dec 10, 2013 at 8:24 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: On Wed, Dec 11, 2013 at 2:46 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 12/10/13 6:30 PM, Jonas Sicking wrote: I would also think that you need properties to position the ::popout. Oh, yes. The extra fun here is:

Re: [manifest] HTTP-based solution for loading manifests

2013-12-11 Thread Bjoern Hoehrmann
* Julian Reschke wrote: On 2013-12-11 19:59, Marcos Caceres wrote: https://github.com/w3c/manifest/issues/98#issuecomment-30293586 I see the comment but I have no idea what he's talking about. The spec is generic; and the IANA registry

Re: [manifest] HTTP-based solution for loading manifests

2013-12-11 Thread Mark Nottingham
RFC5988 defines a model for linking (context, relation, target), as well as the Link header as *one* possible way to convey those links. There are many other possible ways to convey links; e.g., HTML link, atom:link, scribbled on the side of a shoebox, the various JSON linking proposals, etc.

Re: [custom elements] Improving the name of document.register()

2013-12-11 Thread Dominic Cooney
On Thu, Dec 12, 2013 at 5:17 AM, pira...@gmail.com pira...@gmail.comwrote: I have seen registerProtocolHandler() and it's being discused registerServiceWorker(). I believe registerElementDefinition() or registerCustomElement() could help to keep going on this path. Send from my Samsung

Re: [custom elements] Improving the name of document.register()

2013-12-11 Thread Scott Miles
I also agree with Ted. I prefer 'registerElement' because I'm used to the concept of registration wrt custom elements, but I'm not ginding any axe. Scott On Wed, Dec 11, 2013 at 6:46 PM, Dominic Cooney domin...@google.com wrote: On Thu, Dec 12, 2013 at 5:17 AM, pira...@gmail.com

Re: IndexedDB: Syntax for specifying persistent/temporary storage

2013-12-11 Thread Jonas Sicking
Hi All, Thanks Jan for sending this. Now let me throw a giant wrench into this discussion :-) Unfortunately as we've been discussing webapps, manifests etc at mozilla I've slowly come to the realization that the temporary/persistent categorization isn't really fulfilling all the envisioned use

Re: [custom elements] Improving the name of document.register()

2013-12-11 Thread Ryosuke Niwa
On Dec 11, 2013, at 6:46 PM, Dominic Cooney domin...@google.com wrote: On Thu, Dec 12, 2013 at 5:17 AM, pira...@gmail.com pira...@gmail.com wrote: I have seen registerProtocolHandler() and it's being discused registerServiceWorker(). I believe registerElementDefinition() or

Re: IndexedDB: Syntax for specifying persistent/temporary storage

2013-12-11 Thread Kinuko Yasuda
Hi, I'm glad to hear that IDB's going to support storage types! On Thu, Dec 12, 2013 at 12:39 PM, Jonas Sicking jo...@sicking.cc wrote: Hi All, Thanks Jan for sending this. Now let me throw a giant wrench into this discussion :-) Unfortunately as we've been discussing webapps,