Re: [whatwg] WebSocket sub protocol name.

2009-12-07 Thread Ian Hickson
On Mon, 7 Dec 2009, Fumitoshi Ukai (��~\飼�~V~G�~U~O) wrote: Control characters are allowed (though using them would be silly). Why are control characters (except LF and CR) allowed? There doesn't seem to be a good reason to exclude them, and excluding them would lead to a

Re: [whatwg] WebSocket sub protocol name.

2009-12-07 Thread Julian Reschke
Ian Hickson wrote: ... And, why is it limited to ASCII instead of UTF-8? Because the HTTP working group refuse to allow UTF-8 in HTTP headers for reasons that I don't really understand, and the handshake is supposed to be valid HTTP. ... A change of the default encoding would be

Re: [whatwg] WebSocket sub protocol name.

2009-12-07 Thread 鵜飼文敏
On Mon, Dec 7, 2009 at 5:05 PM, Ian Hickson i...@hixie.ch wrote: On Mon, 7 Dec 2009, Fumitoshi Ukai (榈~\椋兼~V~G鎫U~O) wrote: Control characters are allowed (though using them would be silly). Why are control characters (except LF and CR) allowed? There doesn't seem to be a

[whatwg] Interface objects defined in Web Workers outside workers

2009-12-07 Thread Simon Pieters
It's not clear from the Web Workers spec which interface objects and constructors should be available to the non-worker context. Worker and SharedWorker obviously should be available, but what about AbstractWorker and the others? I think Worker, SharedWorker and ErrorEvent should probably

[whatwg] Inconsistent naming for interfaces in workers

2009-12-07 Thread Simon Pieters
The Navigator and WorkerLocation interfaces in workers have inconsistent naming. Please rename the Navigator interface to WorkerNavigator. -- Simon Pieters Opera Software

[whatwg] Inconsistent behavior for empty-string URLs

2009-12-07 Thread Nicholas Zakas
Hi, In a recent investigation into capacity issues, I found that there are several instances where the browser will make a second to the page based on resolving empty-string URLs in the several tags. I tested four instances: img src=, link href=, script src=, and iframe src=. Across major

Re: [whatwg] Inconsistent behavior for empty-string URLs

2009-12-07 Thread Aryeh Gregor
On Mon, Dec 7, 2009 at 1:51 PM, Nicholas Zakas nza...@yahoo-inc.com wrote: Presently, HTML5 does provide guidance on the correct behavior for img src=”” in section 4.8.2, indicating that Firefox 3.5’s and Opera 10’s behavior in this regard is correct: “If the base URI of the element is the

Re: [whatwg] Inconsistent behavior for empty-string URLs

2009-12-07 Thread Nicholas Zakas
Thanks for the references, this helps my understanding a lot. The reason I think this is important is because the just fetch the resource again behavior is inherently destructive and unexpected. When one of these appears on a page, page views double. This isn't a problem if it's your personal

[whatwg] [WebWorkers] Maximum number of workers (was About the delegation example)

2009-12-07 Thread David Bruant
David Bruant : In the delegation example, the number of workers chosen is an arbitrary 10. But, in a single-core processor, having only one worker will result in more or less the same running time, because at the end, each worker runs on the only core. Ian Hickson : That depends on the

Re: [whatwg] [Web workers] An attribute describing the best number of worker to invoke in a delegation use case

2009-12-07 Thread David Bruant
Ian Hickson a écrit : On Wed, 11 Nov 2009, David Bruant wrote: This is a new proposal taking into account the feedback I recieved to the [WebWorkers] About the delegation example message. In the delegation example of the WebWorker spec, we can see this line : var num_workers = 10; My

Re: [whatwg] [WebWorkers] Maximum number of workers (was About the delegation example)

2009-12-07 Thread Drew Wilson
We discussed this previously ( http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-July/020865.html) - the consensus was that since the Worker APIs are inherently asynchronous, user agents were free to impose limits on worker creation (and queue up new creation requests when the limit has

[whatwg] Passing mouse events through the transparent parts of a canvas tag

2009-12-07 Thread Gregg Tavares
Excuse me if this has already been discussed Has there been a proposal for allowing mouse events to go through a canvas element where it is transparent to the element below? As an example, assume you have a canvas element with a triangle rendered into the top left corner so that half the canvas

Re: [whatwg] [WebWorkers] Advocation to provide the DOM API to the workers

2009-12-07 Thread David Bruant
The reason WebWorkers don't have access to the DOM is concurrency. For example, to loop through a list of children I need to first read the number of childrens, then have a for loop which starts at 0 and ends at length-1. If you have two threads that can access the DOM concurrently, then one

Re: [whatwg] Passing mouse events through the transparent parts of a canvas tag

2009-12-07 Thread Jason Oster
On Dec 7, 2009, at 5:32 PM, Gregg Tavares wrote: Excuse me if this has already been discussed Has there been a proposal for allowing mouse events to go through a canvas element where it is transparent to the element below? As an example, assume you have a canvas element with a triangle

Re: [whatwg] WebSocket sub protocol name.

2009-12-07 Thread 鵜飼文敏
On Mon, Dec 7, 2009 at 7:25 PM, Ian Hickson i...@hixie.ch wrote: On Mon, 7 Dec 2009, Fumitoshi Ukai (�µ~\飼æ~V~Gæ~U~O) wrote: On Mon, Dec 7, 2009 at 5:05 PM, Ian Hickson i...@hixie.ch wrote: On Mon, 7 Dec 2009, Fumitoshi Ukai (榈~\椋兼~V~G鎫U~O) wrote: Control characters are

Re: [whatwg] Inconsistent behavior for empty-string URLs

2009-12-07 Thread Jonas Sicking
On Mon, Dec 7, 2009 at 10:51 AM, Nicholas Zakas nza...@yahoo-inc.com wrote: Hi, In a recent investigation into capacity issues, I found that there are several instances where the browser will make a second to the page based on resolving empty-string URLs in the several tags. I tested four

Re: [whatwg] Passing mouse events through the transparent parts of a canvas tag

2009-12-07 Thread Jonas Sicking
On Mon, Dec 7, 2009 at 7:15 PM, Jason Oster paras...@kodewerx.org wrote: On Dec 7, 2009, at 5:32 PM, Gregg Tavares wrote: Excuse me if this has already been discussed Has there been a proposal for allowing mouse events to go through a canvas element where it is transparent to the element

Re: [whatwg] WebSocket sub protocol name.

2009-12-07 Thread Ian Hickson
On Tue, 8 Dec 2009, Fumitoshi Ukai (��~\飼�~V~G�~U~O) wrote: protocol now accepts U+0020. Is it ok to use U+0020 only in /protocol/ ? (e.g. new WebSocket(ws://example.com/, ); ) It seems space is optional after colon in field of handshake message, how can we distinguish U+0020 and U+0020