https://www.w3.org/Bugs/Public/show_bug.cgi?id=24316
Bug ID: 24316
Summary: [Shadow]: implement :ancestor and change :host
behavior
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
St
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24087
Dimitri Glazkov changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Thu, Jan 16, 2014 at 10:42 AM, Anne van Kesteren wrote:
> On Wed, Jan 15, 2014 at 10:26 PM, Tab Atkins Jr. wrote:
>> As a voice of dissent, I *really like* the "return P, and complete the
>> rest of these steps asynchronously" pattern. It's just your
>> "algorithm A and B" pattern, but put in
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24314
Bug ID: 24314
Summary: [Custom]: enteredView and leftView callbacks are still
confusing
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
On 1/16/14 1:29 PM, Domenic Denicola wrote:
Hmm, I don't quite understand the concern.
You're creating new objects using things like Promise.cast(). That will
create an object whose prototype is Promise.prototype. But which
realm's Promise is it using in this case? That needs to be specifi
On Wed, Jan 15, 2014 at 10:26 PM, Tab Atkins Jr. wrote:
> As a voice of dissent, I *really like* the "return P, and complete the
> rest of these steps asynchronously" pattern. It's just your
> "algorithm A and B" pattern, but put in a single list. Having the
> sync section entirely before the as
From: Boris Zbarsky
> All the terms in the "Creating Promises" are implicitly assuming operation in
> a particular realm [1]. Same for the ones in "Aggregating Promises" and the
> definition of "Transforming p with onFulfilled and onRejected". Same thing
> for the "Promise Arguments Should B
On 1/14/14 7:33 AM, Arthur Barstow wrote:
[2]:
https://github.com/domenic/promises-unwrapping/blob/master/docs/writing-specifications-with-promises.md
One issue I just realized, as I was considering how to implement some of
this stuff in automated ways. All the terms in the "Creating Promises
Congratulations Anne on today's publication of the CORS Recommendation!
Thanks to you, all of the contributors [1] and to WebAppSec for pushing
this through.
-Cheers, ArtB
[1] <http://www.w3.org/TR/2014/REC-cors-20140116/#acknowledgments>
On 1/16/14 11:57 AM, ext Coralie Mercie
