[PE] interface MessageEvent : ProgressEvent

2012-11-16 Thread Jungkee Song
Hi, While mulling over the usage of PE event, I came up with a suggestion. As the data attribute of message event delivers structured objects including File Blob and ArrayBuffer objects, authors might need a primitive way of checking the progress of message load. I think the MessageEvent

CfC: Selectors API Level 1 Test Suite; deadline November 23

2012-11-16 Thread Arthur Barstow
The RfR for the Selectors API Level 1 test suite passed WebApps' testing group's review (see below), and according to the agreed #Approvalprocess, this now means a group wide review should be done. As such, this is a CfC for this test suite:

Re: [PE] interface MessageEvent : ProgressEvent

2012-11-16 Thread Anne van Kesteren
On Fri, Nov 16, 2012 at 12:48 AM, Jungkee Song jungkee.s...@samsung.com wrote: I think the MessageEvent interface derived from ProgressEvent interface would solve many such use cases. It seems we already have candidates: server-sent events, web socket, cross-document messaging, channel

Re: Call for Consensus: CORS to Candidate Recommendation

2012-11-16 Thread Arthur Barstow
On 11/15/12 5:31 PM, ext Hill, Brad wrote: I have placed a draft for review at: http://www.w3.org/2011/webappsec/cors-draft/ And this is a Call for Consensus among the WebAppSec and WebApps WGs to take this particular text (with necessary additions to the Status of this Document section if

Re: Call for Consensus: CORS to Candidate Recommendation

2012-11-16 Thread Glenn Adams
Before going to CR, I believe the [HTML] entry in the references section needs to be changed to reference an appropriate W3C specification. A present, it reference a non-W3C document. On Fri, Nov 16, 2012 at 6:17 AM, Arthur Barstow art.bars...@nokia.comwrote: On 11/15/12 5:31 PM, ext Hill, Brad

Re: Call for Consensus: CORS to Candidate Recommendation

2012-11-16 Thread Ms2ger
I object to making such a change. On 11/16/2012 02:32 PM, Glenn Adams wrote: Before going to CR, I believe the [HTML] entry in the references section needs to be changed to reference an appropriate W3C specification. A present, it reference a non-W3C document. On Fri, Nov 16, 2012 at 6:17 AM,

Re: Call for Consensus: CORS to Candidate Recommendation

2012-11-16 Thread Glenn Adams
Cox will file an FO (as a W3C member) if it is not fixed. On Fri, Nov 16, 2012 at 6:51 AM, Ms2ger ms2...@gmail.com wrote: I object to making such a change. On 11/16/2012 02:32 PM, Glenn Adams wrote: Before going to CR, I believe the [HTML] entry in the references section needs to be

[admin] Publication Rules [Was Re: Call for Consensus: CORS to Candidate Recommendation]

2012-11-16 Thread Arthur Barstow
The W3C's process documents (e.g. #PubRules) define the policies for publications and this issue will be addressed if/when the CR is actually published. WebApps is simply a user of the publication policy. If you want to discuss W3C processes such as PubRules, please use some other list - and

Re: [admin] Publication Rules [Was Re: Call for Consensus: CORS to Candidate Recommendation]

2012-11-16 Thread Glenn Adams
Unless I've missed it, I don't believe the #PubRules provides guidelines on what documents are referenced by a spec and whether the reference is normative or non-normative. If I'm wrong, please point out the policy or pubrules text that addresses this issue. Just to be clear, I don't object to

random numbers API

2012-11-16 Thread Florian Bösch
Motivation: Web Applications enter the arena of interactive content creation/consumption (games, productivity software, etc.). A good PRNG would be desirable in many situations. Web Applications that desire to use random numbers have a 4 problems with the existing Math.random function. 1) The

Re: random numbers API

2012-11-16 Thread Anne van Kesteren
On Fri, Nov 16, 2012 at 7:13 AM, Florian Bösch pya...@gmail.com wrote: Motivation: Web Applications enter the arena of interactive content creation/consumption (games, productivity software, etc.). A good PRNG would be desirable in many situations. Did you discuss this with TC39? --

Re: random numbers API

2012-11-16 Thread Frederick.Hirsch
The W3C Web Cryptography working group [1] has a draft that seems to include a method to generate cryptographically random values [2]. I'm not sure how well that relates to what your use case requires but it might be worth looking at. regards, Frederick Frederick Hirsch Nokia [1]

Re: random numbers API

2012-11-16 Thread Florian Bösch
On Fri, Nov 16, 2012 at 4:22 PM, Anne van Kesteren ann...@annevk.nl wrote: Did you discuss this with TC39? I did not, sorry if this is the wrong place for it.

Re: random numbers API

2012-11-16 Thread Florian Bösch
On Fri, Nov 16, 2012 at 4:24 PM, frederick.hir...@nokia.com wrote: The W3C Web Cryptography working group [1] has a draft that seems to include a method to generate cryptographically random values [2]. It does include a random number generator. However it does not include seeding and

Re: random numbers API

2012-11-16 Thread David Bruant
Le 16/11/2012 16:30, Florian Bösch a écrit : On Fri, Nov 16, 2012 at 4:24 PM, frederick.hir...@nokia.com mailto:frederick.hir...@nokia.com wrote: The W3C Web Cryptography working group [1] has a draft that seems to include a method to generate cryptographically random values [2]. It

Re: random numbers API

2012-11-16 Thread Florian Bösch
On Fri, Nov 16, 2012 at 5:20 PM, David Bruant bruan...@gmail.com wrote: That'd be a nonsense to add seeding in my opinion. If you want security, you don't want to take the risk of people seeding and loose all security property. If it's for debugging purposes, the seeding should be part of a

Re: random numbers API

2012-11-16 Thread Boris Zbarsky
On 11/16/12 7:13 AM, Florian Bösch wrote: 4) Alternative implementations in JS suffer even in the presence of sophisticated JITing VMs from the fact that mathematics is done in doubles (in the case of addition, subtraction, division and multiplication) and by converting double - int - double (in

Re: random numbers API

2012-11-16 Thread David Bruant
Le 16/11/2012 17:35, Florian Bösch a écrit : On Fri, Nov 16, 2012 at 5:20 PM, David Bruant bruan...@gmail.com mailto:bruan...@gmail.com wrote: That'd be a nonsense to add seeding in my opinion. If you want security, you don't want to take the risk of people seeding and loose all

Re: random numbers API

2012-11-16 Thread Florian Bösch
I'll see that I can come up with a test suite that verifies statistical and runtime behavior of an array of algorithms implemented in JS, it'll probably take a while. On Fri, Nov 16, 2012 at 6:02 PM, David Bruant bruan...@gmail.com wrote: Le 16/11/2012 17:35, Florian Bösch a écrit : On Fri,

Re: random numbers API

2012-11-16 Thread Joshua Bell
On Fri, Nov 16, 2012 at 9:20 AM, Florian Bösch pya...@gmail.com wrote: I'll see that I can come up with a test suite that verifies statistical and runtime behavior of an array of algorithms implemented in JS, it'll probably take a while. Thank you! As a side benefit, having a library of

Re: random numbers API

2012-11-16 Thread David Bruant
Le 16/11/2012 18:20, Florian Bösch a écrit : I'll see that I can come up with a test suite that verifies statistical and runtime behavior of an array of algorithms implemented in JS, it'll probably take a while. I don't think you need to go through such lengths. If you do have the galaxy use

Re: exposing CANVAS or something like it to Web Workers

2012-11-16 Thread Ian Hickson
On Mon, 14 May 2012, Gregg Tavares (�~K�) wrote: I'd like to work on exposing something like CANVAS to web workers. Ideally how over it works I'd like to be able to *) get a 2d context in a web worker *) get a WebGL context in a web worker *) download images in a web worker and the

Re: exposing CANVAS or something like it to Web Workers

2012-11-16 Thread Charles Pritchard
On Nov 16, 2012, at 1:50 PM, Ian Hickson i...@hixie.ch wrote: On Mon, 14 May 2012, Gregg Tavares (�~K�) wrote: I'd like to work on exposing something like CANVAS to web workers. Ideally how over it works I'd like to be able to *) get a 2d context in a web worker *) get a WebGL context

Re: exposing CANVAS or something like it to Web Workers

2012-11-16 Thread Ian Hickson
On Fri, 16 Nov 2012, Charles Pritchard wrote: http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Nov/0199.html Seems like we might use requestAnimationFrame in the main thread to postMessage to the worker as an alternative to using setInterval in workers for repaints.