Re: Request for feedback: Streams API

2013-12-09 Thread Takeshi Yoshino
Thanks. ByteStream is already partially implemented in Blink/Chromium. As one of implementors, I'll continue prototyping and share issues here. I haven't got time for, but writing some polyfill might be also good thing to do. Takeshi On Thu, Dec 5, 2013 at 2:38 AM, Kenneth Russell

Re: Comments on version web-apps specs from 2013-10-31

2013-12-09 Thread Takeshi Yoshino
Thanks for feedback. On Thu, Nov 21, 2013 at 4:56 PM, Feras Moussa feras.mou...@hotmail.comwrote: Hi Francois, Thanks for the feedback. From: francois-xavier.kowal...@hp.com To: public-webapps@w3.org Date: Wed, 20 Nov 2013 20:30:47 + Subject: Comments on version web-apps specs

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-09 Thread Kornel Lesiński
On 9 December 2013 09:33:47 Yoav Weiss y...@yoav.ws wrote: IMO, it might be better not to define an explicit way to inline the manifest, and let authors simply use data URIs to do that, if they see such a need. e.g. link rel=manifest href=data:application/manifest+json,{ ... } If this becomes

Re: New manifest spec - ready for FPWD?

2013-12-09 Thread Mounir Lamouri
On Wed, Dec 4, 2013, at 10:03, Marcos Caceres wrote: From the research we’ve done, none of the proprietary solutions currently do this. I’ve added this as a feature request [1] so we can see how much interest there is. I think it is exaggerated to say that pages rely on the user seeing the

Fwd: Re: Please review the updated Streams API

2013-12-09 Thread Harald Alvestrand
Rob Manson sent out a request to the WEBRTC WG's mailing list for review of the implications of the Stream API to WEBRTC. Arthur Barstow asked for comments to be sent to public-webapps@w3.org, so I'm forwarding my response here. Original Message Subject:Re: Please

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

2013-12-09 Thread Mounir Lamouri
On Mon, Dec 9, 2013, at 20:33, Yoav Weiss wrote: IMO, it might be better not to define an explicit way to inline the manifest, and let authors simply use data URIs to do that, if they see such a need. e.g. link rel=manifest href=data:application/manifest+json,{ ... } If this becomes a

Re: [webcomponents] Auto-creating shadow DOM for custom elements

2013-12-09 Thread Scott Miles
Domenic Denicola a few messages back gave a highly cogent explanation of the exact line of thinking arrived at last time we went through all this material. I'm not wont to try to summarize it here, since he said it already better there. Perhaps the short version is: nobody knows what the

Re: [webcomponents] Auto-creating shadow DOM for custom elements

2013-12-09 Thread Rob Eisenberg
I'm late to the party...so pardon if this is a dumb idea but Could the solution to this problem be as simple as adding an applyTemplate callback to the lifecycle and prohibiting access to the shadowRoot prior to that point in time? On Mon, Dec 9, 2013 at 2:13 PM, Scott Miles

Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)

2013-12-09 Thread Ryosuke Niwa
On Dec 8, 2013, at 4:42 PM, Dominic Cooney domin...@google.com wrote: On Sun, Dec 8, 2013 at 7:25 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 7, 2013, at 4:38 PM, Dominic Cooney domin...@google.com wrote: On Fri, Dec 6, 2013 at 3:34 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 5, 2013, at

[Bug 24042] New: [imports]: Parser should not wait on external resources inside imports

2013-12-09 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24042 Bug ID: 24042 Summary: [imports]: Parser should not wait on external resources inside imports Product: WebAppsWG Version: unspecified Hardware: PC OS:

[Bug 24043] New: [Custom]: Need to check writable too.

2013-12-09 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24043 Bug ID: 24043 Summary: [Custom]: Need to check writable too. Product: WebAppsWG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal

Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)

2013-12-09 Thread Dominic Cooney
On Tue, Dec 10, 2013 at 6:38 AM, Ryosuke Niwa rn...@apple.com wrote: On Dec 8, 2013, at 4:42 PM, Dominic Cooney domin...@google.com wrote: On Sun, Dec 8, 2013 at 7:25 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 7, 2013, at 4:38 PM, Dominic Cooney domin...@google.com wrote: On Fri, Dec

Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)

2013-12-09 Thread Brendan Eich
Ryosuke Niwa wrote: As for the social endorse button, I've never seen a popular SNS share buttons implemented using HTML button elements; most of them add their own DOM to add icons, etc... Right you are. And there's a deeper reason why like (endorse, LOL) buttons use iframes: the ability to

Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)

2013-12-09 Thread Elliott Sprehn
On Mon, Dec 9, 2013 at 5:50 PM, Brendan Eich bren...@secure.meer.netwrote: Ryosuke Niwa wrote: As for the social endorse button, I've never seen a popular SNS share buttons implemented using HTML button elements; most of them add their own DOM to add icons, etc... Right you are. And

Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)

2013-12-09 Thread Ryosuke Niwa
On Dec 9, 2013, at 5:12 PM, Dominic Cooney domin...@google.com wrote: On Tue, Dec 10, 2013 at 6:38 AM, Ryosuke Niwa rn...@apple.com wrote: On Dec 8, 2013, at 4:42 PM, Dominic Cooney domin...@google.com wrote: On Sun, Dec 8, 2013 at 7:25 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 7, 2013,

Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)

2013-12-09 Thread Tab Atkins Jr.
On Tue, Dec 10, 2013 at 3:33 PM, Ryosuke Niwa rn...@apple.com wrote: In fact, why do we even bother to add any new API at all for web components if our primary target was framework authors. Ember.js, Angular JS, etc... all work great already because they add an abstraction layer on top of DOM.

Re: [webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)

2013-12-09 Thread Ryosuke Niwa
On Dec 9, 2013, at 8:45 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: On Tue, Dec 10, 2013 at 3:33 PM, Ryosuke Niwa rn...@apple.com wrote: In fact, why do we even bother to add any new API at all for web components if our primary target was framework authors. Ember.js, Angular JS, etc... all

Re: [webcomponents] Auto-creating shadow DOM for custom elements

2013-12-09 Thread Ryosuke Niwa
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 the short version is: nobody knows what the 'standard use case' is yet. How is that possible given we've already spent 2+ years on the

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

2013-12-09 Thread Ryosuke Niwa
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 the short version is: nobody knows what the 'standard use case' is yet.

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

2013-12-09 Thread Ryosuke Niwa
On Dec 9, 2013, at 11:03 PM, Matthew McNulty mmcnu...@google.com wrote: 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