W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

[Bug 22522] WebIDL, error handling, and promises

From: <bugzilla@jessica.w3.org>
Date: Mon, 01 Jul 2013 22:20:45 +0000
To: public-script-coord@w3.org
Message-ID: <bug-22522-3890-Du0Lpjuk6g@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22522

Mark S. Miller <erights@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erights@gmail.com

--- Comment #8 from Mark S. Miller <erights@gmail.com> ---
(In reply to comment #7)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > (In reply to comment #3)
> > > > Well it does depend on HTML's event loop. JavaScript doesn't define such a
> > > > thing anywhere.
> > > 
> > > That sounds like more reason to push it down the stack :) If the largest
> > > consumers of JS (Web/Node) both depend on the loop, this might encourage
> > > them to standardize it... which would be great as standardizing the event
> > > loop might provide an API to hook into it properly (instead of using
> > > setTimeout and matchMedia hacks).
> > 
> > TC39 is already planning to standardize the event loop in ES7, I believe. 
> > They don't need any further encouragement from us.

Encouragement is always appreciated ;).


> 
> 
> The event loop will be specified as part of ES6.

ES6 is likely only to specify the minimal placeholder of an event loop as
necessary to specify module loaders. The full event loop spec is indeed likely
to be in ES7.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 1 July 2013 22:20:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:50 UTC