Re: Proposal for User Agent Augmented Authorization

2014-08-11 Thread Sam Penrose
In response to feedback, I have tightened the purpose of the API to: 1) making Oauth-based authentication work better for web apps by 2) augmenting existing redirect and cookie policies so as to 3) enable single sign on and 4) enable identity management interfaces in user agents. To that

RE: User Intentions Explainer (was: List of Intentions)

2014-08-11 Thread Ben Peters
I agree with this. We should have a single 'shape' for these events and shared terminology. I think trying to solve all of the problems in one complete spec would be too complex, but if we use an Intentions Explainer to divide the problem into manageable pieces, we can continue on our traject

Re: Blocking message passing for Workers

2014-08-11 Thread Jeffrey Walton
On Mon, Aug 11, 2014 at 7:52 PM, David Bruant wrote: > Le 12/08/2014 00:40, Glenn Maynard a écrit : > > On Sat, Aug 9, 2014 at 9:12 AM, David Bruant wrote: >> >> This topic is on people minds [1]. My understanding of where we're at is >> that "ECMAScript 7" will bring syntax (async/await keywords

Re: Blocking message passing for Workers

2014-08-11 Thread Brendan Eich
David Bruant wrote: Le 09/08/2014 16:22, Brian Kardell a écrit : On Aug 9, 2014 10:16 AM, "David Bruant" > wrote: > There is still a case for blocking primitives for projects that compile from other languages (C, C++, Python, Java, C#, etc.) to JS [3]. > I'm glad t

Re: Blocking message passing for Workers

2014-08-11 Thread David Bruant
Le 09/08/2014 16:22, Brian Kardell a écrit : On Aug 9, 2014 10:16 AM, "David Bruant" > wrote: > There is still a case for blocking primitives for projects that compile from other languages (C, C++, Python, Java, C#, etc.) to JS [3]. > I'm glad to be switching last n

Re: Blocking message passing for Workers

2014-08-11 Thread David Bruant
Le 12/08/2014 00:40, Glenn Maynard a écrit : On Sat, Aug 9, 2014 at 9:12 AM, David Bruant > wrote: This topic is on people minds [1]. My understanding of where we're at is that "ECMAScript 7" will bring syntax (async/await keywords [2]) that looks like sync

Re: Blocking message passing for Workers

2014-08-11 Thread Glenn Maynard
On Sat, Aug 9, 2014 at 9:12 AM, David Bruant wrote: > This topic is on people minds [1]. My understanding of where we're at is > that "ECMAScript 7" will bring syntax (async/await keywords [2]) that looks > like sync syntax, but acts asynchronously. This should eliminate the need > for web devs f

Re: Screen Orientation Feedback

2014-08-11 Thread Jonas Sicking
On Fri, Aug 8, 2014 at 6:44 AM, Mounir Lamouri wrote: > Maybe this feedback should be more for DeviceOrientation than Screen > Orientation. There has been a few discussions there > (public-geolocation). This is the type of procedural issues that I'd really rather not get caught in. I think it's f

Re: Screen Orientation Feedback

2014-08-11 Thread Rich Tibbett
On Tue, Aug 5, 2014 at 11:14 PM, Jonas Sicking wrote: > Hi All, > > I think the current interaction between the screen orientation and > device orientation specs is really unfortunate. > > Any time that you use the device orientation in order to render > something on screen, you have to do non-obv

Re: File API: reading a Blob

2014-08-11 Thread Anne van Kesteren
On Fri, Aug 8, 2014 at 5:56 PM, Arun Ranganathan wrote: > I strongly think we should leave FileReaderSync and FileReader alone. Also > note that FileReaderSync and XHR (sync) are not different, in that both don’t > do partial data. But we should have a stream api that evolves to read, and it >

[Bug 26552] New: [Shadow]: consider supporting :first-child, nth-child() in content select

2014-08-11 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26552 Bug ID: 26552 Summary: [Shadow]: consider supporting :first-child, nth-child() in content select Product: WebAppsWG Version: unspecified Hardware: PC OS: