Reminder: RfC: LCWD of Pointer Lock; deadline November 28

2013-11-22 Thread Arthur Barstow
Original Message Subject:RfC: LCWD of Pointer Lock; deadline November 28 Resent-Date:Thu, 31 Oct 2013 19:36:52 + Resent-From:public-webapps@w3.org Date: Thu, 31 Oct 2013 15:32:49 -0400 From: ext Arthur Barstow art.bars...@nokia.com To: public-webapps

Re: CfC: publish Candidate Recommendation of File API; deadline November 28

2013-11-22 Thread Charles McCathie Nevile
On Thu, 21 Nov 2013 19:44:29 +0100, Arthur Barstow art.bars...@nokia.com wrote: Hi All, Arun completed processing the comments [Comments] for the Last Call version of File API [LCWD]. Although the comments resulted in changes to the spec (see [Diff]), no new features were added and the

Re: Sync IO APIs in Shared Workers

2013-11-22 Thread Glenn Maynard
On Thu, Nov 21, 2013 at 8:33 PM, Jonas Sicking jo...@sicking.cc wrote: One of the arguments made against sync APIs in workers made in [1] is that even for workers, it is often important to keep code responsive in order to react to actions taken by the user. The only relevant thing I can dig

Re: [HTML Imports]: Sync, async, -ish?

2013-11-22 Thread John J Barton
I agree that we should allow developers to set 'sync' attribute on link tags to block rendering until load. That will allow them to create sites that appear to load slowly rather than render their standard HTML/CSS. I think that the default should be the current solution and 'sync' should be

Re: [HTML Imports]: Sync, async, -ish?

2013-11-22 Thread Daniel Buchner
Personally I don't have any issues with this solution, it provides for the use-cases we face. Also, it isn't without precedent - you can opt for a sync XMLHttpRequest (not much different). The best part of an explicit 'sync' attribute, is that we can now remove the block if a script comes after

Re: [HTML Imports]: Sync, async, -ish?

2013-11-22 Thread John J Barton
On Fri, Nov 22, 2013 at 8:22 AM, Daniel Buchner dan...@mozilla.com wrote: Personally I don't have any issues with this solution, it provides for the use-cases we face. Also, it isn't without precedent - you can opt for a sync XMLHttpRequest (not much different). The best part of an explicit

Re: [HTML Imports]: Sync, async, -ish?

2013-11-22 Thread Jonas Sicking
On Nov 22, 2013 8:24 AM, Daniel Buchner dan...@mozilla.com wrote: Personally I don't have any issues with this solution, it provides for the use-cases we face. Also, it isn't without precedent - you can opt for a sync XMLHttpRequest (not much different). Except that sync XHR is considered one

Re: [HTML Imports]: Sync, async, -ish?

2013-11-22 Thread Daniel Buchner
I'm not talking about the script blocking as usual - I'm referencing the presence of a script causing the import to block until completed, when the script follows it. On Fri, Nov 22, 2013 at 8:57 AM, John J Barton johnjbar...@johnjbarton.comwrote: On Fri, Nov 22, 2013 at 8:22 AM, Daniel

Re: [HTML Imports]: Sync, async, -ish?

2013-11-22 Thread Daniel Buchner
Of course I realize this Jonas, but I assure you, if you burden the most common use-cases with poor ergonomics, developers will find even more ghastly ways to degrade perf. Can someone post an overview of the proposed solutions, and how they apply to the use-cases stated a few posts back? On

Re: Sync IO APIs in Shared Workers

2013-11-22 Thread Jonas Sicking
On Fri, Nov 22, 2013 at 7:54 AM, Glenn Maynard gl...@zewt.org wrote: But, we should explore the use cases more thoroughly first, to see if this is really needed. An alternative is to just terminate() the whole worker and start a new one. That's not very elegant, but it's very simple and

[testing] Seeking Test Facilitator(s) for Indexed Database API

2013-11-22 Thread Arthur Barstow
[ Bcc: public-webapps-testsuite ] Hi All, We need help with the Indexed Database API testing effort. The general expectations for a Test Facilitator (TF) are defined in the testing Roles wiki [Roles]. For this spec, one of the first steps is to review the various submissions and recommend

Re: Sync IO APIs in Shared Workers

2013-11-22 Thread Glenn Maynard
On Fri, Nov 22, 2013 at 11:55 AM, Jonas Sicking jo...@sicking.cc wrote: On Fri, Nov 22, 2013 at 7:54 AM, Glenn Maynard gl...@zewt.org wrote: But, we should explore the use cases more thoroughly first, to see if this is really needed. An alternative is to just terminate() the whole worker

RTC in Web workers

2013-11-22 Thread Charles Pritchard
Should RTC data channels be available in Workers and/or SharedWorker? Mainly: self.RTCPeerConnection self.RTCSessionDescription WebSocket and XHR are available, seems like RTC ought to be but isn't. -Charles

Re: Sync IO APIs in Shared Workers

2013-11-22 Thread Simon Pieters
On Fri, 22 Nov 2013 03:33:51 +0100, Jonas Sicking jo...@sicking.cc wrote: The only browser shipping SharedWorkers is Chrome (not sure if Opera does too?), Yes, both Presto-based (since Opera 10.60) and Chromium-based. -- Simon Pieters Opera Software