On Thu, Oct 10, 2013 at 9:30 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
On Thu, Oct 10, 2013 at 1:06 AM, Anne van Kesteren ann...@annevk.nl wrote:
Either that or let it have its own node type if it's going to be
incompatible with DocumentFragment in terms of behavior. Alternatively
we
On Thu, Oct 10, 2013 at 11:34 PM, Feras Moussa feras.mou...@hotmail.comwrote:
Apologies for the delay, I had broken one of my mail rules and didn't see
this initially.
Asymeric is correct - there have been a few threads and revisions. A more
up-to-date version is the one Asymeric linked -
On 10/11/13 8:05 AM, ext Takeshi Yoshino wrote:
On Thu, Oct 10, 2013 at 11:34 PM, Feras Moussa
feras.mou...@hotmail.com mailto:feras.mou...@hotmail.com wrote:
Apologies for the delay, I had broken one of my mail rules and
didn't see this initially.
Asymeric is correct - there have
On Wed, Oct 9, 2013, at 21:10, Joshua Bell wrote:
To do this in a backwards compatible way, we could add an option on
open() that, if an upgrade is required, any other connections are forcibly
closed; instead of a versionchange event the connections would be sent a
close event, similar to the
On 7/31/13 10:05 AM, ext Marcos Caceres wrote:
On Wednesday, July 31, 2013 at 1:07 PM, Yves Lafon wrote:
Thanks, indeed the CR-PR transition was made with a test suite that was
linked to this WebIDL reference, and not the other one.
That said, if you have tests and better, a report for a
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21388
Ted Mielczarek [:ted] t...@mielczarek.org changed:
What|Removed |Added
Status|NEW |RESOLVED
On Wed, Sep 5, 2012 at 7:03 PM, Jonas Sicking jo...@sicking.cc wrote:
Hence I think something like the following would work:
[Constructor]
interface SyncMessageChannel {
readonly attribute MessagePortSyncSide syncPort;
readonly attribute MessagePortAsyncSide asyncPort;
};
interface
* Enable compiling code that was written for other platforms to the
web. Specifically where such code uses synchronous APIs, but where we
for good reasons have chosen not to expose synchronous counterparts in
the web platform. The most obvious example here is synchronous
filesystem access
pira...@gmail.com pira...@gmail.com, 2013-10-11 21:24 +0200:
[Jonas said]:
* Enable compiling code that was written for other platforms to the
web. Specifically where such code uses synchronous APIs, but where we
for good reasons have chosen not to expose synchronous counterparts in
the
On Fri, Oct 11, 2013 at 2:24 PM, pira...@gmail.com pira...@gmail.comwrote:
Synchronous APIs are easier to use since it's how things have been done
since decades ago,
No, they're easier to use because they fit the model of linear human
thought more naturally. The idea that asynchronous APIs
On Friday, October 11, 2013, Arthur Barstow wrote:
On 7/31/13 10:05 AM, ext Marcos Caceres wrote:
On Wednesday, July 31, 2013 at 1:07 PM, Yves Lafon wrote:
Thanks, indeed the CR-PR transition was made with a test suite that was
linked to this WebIDL reference, and not the other one.
That
On Oct 7, 2013, at 1:38 PM, Jonas Sicking jo...@sicking.cc wrote:
On Oct 7, 2013 6:56 AM, Hajime Morrita morr...@google.com wrote:
Hi,
I'm sorry that I didn't notice that you were talking about UA shadow DOM.
It's an implementation detail and the standard won't care about that.
On Fri, Oct 11, 2013 at 10:23 PM, Ryosuke Niwa rn...@apple.com wrote:
On Oct 7, 2013, at 1:38 PM, Jonas Sicking jo...@sicking.cc wrote:
On Oct 7, 2013 6:56 AM, Hajime Morrita morr...@google.com wrote:
Hi,
I'm sorry that I didn't notice that you were talking about UA shadow DOM.
It's an
13 matches
Mail list logo
