Hello!
As a Web developer, I recently dig into the proposed FileSystem API [1]
which cover many use cases except one: How a user can actually allows a web
application to really write something in the user local file system (even
if it's slow). On the other hand, the File API: Writer [2] cover
Should this not be synchronized with the Streams API? Please see recent
evolutions [1] and thread [2] (where WebRTC streams are mentioned)
Ccing Webapps and Takeshi/Feras.
Regarding your proposal I was about to propose to add about the same
thing in Streams: at least a stop method (which
On 10/18/13 11:56, Aymeric Vitte wrote:
Regarding your proposal I was about to propose to add about the same
thing in Streams: at least a stop method (which would send an EOF) and
maybe a resume method, or something like your pause/unpause.
To be clear, the .enabled flag and .stop() method
Hi Jeremie,
Have you seen this proposal?
http://lists.w3.org/Archives/Public/public-script-coord/2013JulSep/0379.html
It's not clear to me if your proposal here is trying to solve problems
that the above proposal doesn't already solve...
Cheers,
Ehsan
On 2013-10-18 8:07 AM, Jeremie
On 10/18/13 6:57 PM, Aymeric Vitte wrote:
Should this not be synchronized with the Streams API? Please see recent
evolutions [1] and thread [2] (where WebRTC streams are mentioned)
I think we're talking about completely different streams, and what Adam
is proposing is applicable for
Le 18/10/2013 19:31, Stefan Håkansson LK a écrit :
I think we're talking about completely different streams, and what Adam
is proposing is applicable for MediaStreamTracks in the context of a
WebRTC PeerConnection.
I don't see why, a stream is a stream, this would be strange that a
Streams API
Le 18/10/2013 19:13, Adam Roach a écrit :
To be clear, the .enabled flag and .stop() method are already there,
and they already pause/unpause the stream and tear it down,
respectively. I'm just proposing concrete semantics for how they
interact with any PeerConnection that the track is
On 10/18/13 12:47, Aymeric Vitte wrote:
Le 18/10/2013 19:13, Adam Roach a écrit :
To be clear, the .enabled flag and .stop() method are already there,
and they already pause/unpause the stream and tear it down,
respectively. I'm just proposing concrete semantics for how they
interact with
Hi!
2013/10/18 Ehsan Akhgari ehsan.akhg...@gmail.com
Hi Jeremie,
Have you seen this proposal? http://lists.w3.org/Archives/**
Public/public-script-coord/**2013JulSep/0379.htmlhttp://lists.w3.org/Archives/Public/public-script-coord/2013JulSep/0379.html
It's not clear to me if your proposal
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23564
Bug ID: 23564
Summary: IDL for open() doesn't match implementation reality
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
On 10/18/2013 11:11 AM, Jeremie Patonnier wrote:
2013/10/18 Ehsan Akhgari ehsan.akhg...@gmail.com
mailto:ehsan.akhg...@gmail.com
Have you seen this proposal?
http://lists.w3.org/Archives/Public/public-script-coord/2013JulSep/0379.html
It's not clear to me if your proposal here
On Sun, Oct 6, 2013 at 9:38 AM, Dimitri Glazkov dglaz...@chromium.org wrote:
So you have link href=blah.html in meh.html and blah.html is:
div id=test/div
script /* how do I get to #test? */ /script
document.currentScript.ownerDocument.querySelector(#test) :)
This only works for code running
they'll have to use a closure to capture the document that the template
lives in
Yes, this is true. But stamping of templates tends to be something custom
elements are really good at, so this paritcular use case doesn't come up
very often.
Out of curiosity, what have the Polymer guys been
I remember Adam raving about HTML Imports being awesome after he tried
them. Adam, can you provide color? :)
:DG
On Fri, Oct 18, 2013 at 4:11 PM, Scott Miles sjmi...@google.com wrote:
they'll have to use a closure to capture the document that the template
lives in
Yes, this is true. But
What I am saying here is that there should be an unique and unified
Streams API supported by all related APIs, each group where it is
relevant should feel concerned instead of thinking another one might be.
Le 18/10/2013 20:04, Adam Roach a écrit :
On 10/18/13 12:47, Aymeric Vitte wrote:
Le
On Fri, Oct 18, 2013 at 11:11 AM, Jeremie Patonnier
jeremie.patonn...@gmail.com wrote:
My proposal does not suggest to do something different than what is
currently possible (except the silent saving). Just to ease the life of Web
dev by avoiding them to work around their usual problem:
-
On Oct 17, 2013, at 10:57 PM, Hayato Ito hay...@chromium.org wrote:
I am aware that there are issues related to selections regarding Shadow DOM
both in the spec and the implementation.
But I don't have a clear answer to resolve that and couldn't satisfy users.
This is one of the toughest
17 matches
Mail list logo
