Re: establishing integration plan for the consumers and producers listed in
the W3C spec, we haven't done anything than what Domenic introduced in this
thread.
I wrote some draft of XHR+ReadableStream integration spec and is
implemented on Chrome, but the plan is not to ship it but wait for the
Fe
Hi,
I'm Program Manager in Internet Explorer Layout team and while investigating
one of the compatibility issues, we've encountered a situation that I'd like to
clarify with the working group.
The behavior we see in Chrome is different from IE/Firefox - the messages
generated by script trigger
This thread was recently re-started at
http://lists.w3.org/Archives/Public/public-webapps/2014OctDec/0084.html
Domenic's latest document is at https://streams.spec.whatwg.org/ The W3C
document has NOT been updated since
http://www.w3.org/TR/2013/WD-streams-api-20131105/ .
/paulc
Paul Cotton
Where is the latest Streams spec?
https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm doesn't have much
about WritableStreams.
Jerry
-Original Message-
From: Domenic Denicola [mailto:dome...@domenicdenicola.com]
Sent: Tuesday, October 14, 2014 10:18 AM
To: Aaron Colwell
Cc: A
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24691
Ian 'Hixie' Hickson changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Cross-posting as before ...
What: IndieUI Task Force Teleconference
When: Wednesday 15 October
2:00 PMSan Francisco -- U.S. Pacific (Daylight) Time (PDT:
UTC -7)
4:00 PMAustin -- U.S. Central (Daylight) Time (CDT: UTC -5)
5:00 PMBoston -
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11587
Anne changed:
What|Removed |Added
Status|NEW |RESOLVED
See Also|
From: Aaron Colwell [mailto:acolw...@google.com]
> MSE is just too far along, has already gone through a fair amount of churn,
> and has major customers like YouTube and Netflix that I just don't want to
> break or force to migrate...again.
Totally understandable.
> I haven't spent much time
On Tue, Oct 14, 2014 at 9:19 AM, Domenic Denicola <
dome...@domenicdenicola.com> wrote:
> From: Aaron Colwell [mailto:acolw...@google.com]
>
> > Yes SourceBuffer is shipping and has been for quite some time in Chrome
> and IE.
>
> Hmm, window.SourceBuffer is undefined in Chrome.
>
You can only cr
From: Aaron Colwell [mailto:acolw...@google.com]
> Yes SourceBuffer is shipping and has been for quite some time in Chrome and
> IE.
Hmm, window.SourceBuffer is undefined in Chrome.
> I am NOT going to rework it all to be a WritableStream.
That's a shame, but completely understandable that yo
Yes SourceBuffer is shipping and has been for quite some time in Chrome and
IE. Firefox and Safari have been working on implementations for quite some
time as well. I am NOT going to rework it all to be a WritableStream. I am
just looking to adjust appendStream() to take whatever object replaced t
From: Domenic Denicola [mailto:dome...@domenicdenicola.com]
> The more interesting question is whether BufferSource is shipping
> (unprefixed), since ideally we would make BufferSource a WritableStream.
Sorry, SourceBuffer, not BufferSource---both in this message and the previous
one.
From: annevankeste...@gmail.com [mailto:annevankeste...@gmail.com] On Behalf Of
Anne van Kesteren
> On Mon, Oct 13, 2014 at 10:00 PM, Paul Cotton
> wrote:
>> MSE is in CR and there are shipping implementations.
>
> Yes, but the Stream object is not shipping. Unless Microsoft has a prototype
>
On Mon, Oct 13, 2014 at 10:00 PM, Paul Cotton wrote:
> MSE is in CR and there are shipping implementations.
Yes, but the Stream object is not shipping. Unless Microsoft has a
prototype it is in exactly 0 implementations. So MSE would have to get
out of CR anyway to get that removed (assuming it's
14 matches
Mail list logo
