Re: [whatwg] WebSocket sub protocol name.

2009-12-08 Thread 鵜飼文敏
On Tue, Dec 8, 2009 at 4:59 PM, Ian Hickson i...@hixie.ch wrote: 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

Re: [whatwg] [hybi] WebSocket sub protocol name.

2009-12-08 Thread Yuzo Fujishima
On Tue, Dec 8, 2009 at 4:59 PM, Ian Hickson i...@hixie.ch wrote: 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

Re: [whatwg] [hybi] WebSocket sub protocol name.

2009-12-08 Thread Julian Reschke
Ian Hickson wrote: 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

Re: [whatwg] [hybi] WebSocket sub protocol name.

2009-12-08 Thread Ian Hickson
On Tue, 8 Dec 2009, Yuzo Fujishima wrote: On Tue, Dec 8, 2009 at 4:59 PM, Ian Hickson i...@hixie.ch wrote: 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

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

2009-12-08 Thread Simon Pieters
On Mon, 07 Dec 2009 22:52:41 +0100, Aryeh Gregor simetrical+...@gmail.com wrote: I don't know why img src= has a special exception. It would be possible to look through the svn log to see if there was a helpful commit message, or maybe someone will remember. I seem to remember someone from

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

2009-12-08 Thread Robert O'Callahan
On Mon, Dec 7, 2009 at 10:03 PM, Jonas Sicking jo...@sicking.cc wrote: Indeed. We've talked about using this CSS property as a way to let only the non-transparent parts of an image receive events. Unfortunately if I recall correctly none of the currently defined values of pointer-events fit

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

2009-12-08 Thread Jonas Sicking
On Tue, Dec 8, 2009 at 1:26 AM, Simon Pieters sim...@opera.com wrote: On Mon, 07 Dec 2009 22:52:41 +0100, Aryeh Gregor simetrical+...@gmail.com wrote: I don't know why img src= has a special exception.  It would be possible to look through the svn log to see if there was a helpful commit

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

2009-12-08 Thread Nicholas Zakas
I'd agree with that, I've yet been able to find an example of someone intentionally including an empty-string URL in one of these tags. -Nicholas __ Commander Lock: Damnit Morpheus, not everyone believes what you believe! Morpheus: My beliefs do not

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

2009-12-08 Thread Nicholas Zakas
The change seems reasonable to me. It just seems that the same change should be made in all cases that cause similar issues, making it the rule of the spec instead of an exception for this one case. Does that make sense? -Nicholas __ Commander Lock:

[whatwg] Proposal for iframe sandbox related change to HTML5 section 4.8.3

2009-12-08 Thread Chris Evans
Hello, I propose changing this text: This flag also prevents script from reading the document.cookie IDL attribute. to This flag also prevents script from reading or writing the document.cookie IDL attribute. This change makes sure the sandbox attribute protects the integrity as well as

[whatwg] boolean attributes in javascript

2009-12-08 Thread Brian Kuhn
How do I correctly set a boolean attributehttp://dev.w3.org/html5/spec/Overview.html#boolean-attributeson a DOM element object in Javascript? var script = document.createElement('script'); 1. script.async = true;// makes the most sense, but appears go against the spec 2.

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Tab Atkins Jr.
On Tue, Dec 8, 2009 at 1:49 PM, Brian Kuhn bnk...@gmail.com wrote: How do I correctly set a boolean attribute on a DOM element object in Javascript? var script = document.createElement('script'); script.async = true;        // makes the most sense, but appears go against the spec

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Brian Kuhn
but it's invalid to set it to anything other than the two values I just mentioned. That's the part I'd like to see changed. I understand that if it's present, it's on. So, why can't async=true be valid? I think all browser vendors will implement it that way anyway. They'd be crazy not to.

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Tab Atkins Jr.
On Tue, Dec 8, 2009 at 3:48 PM, Brian Kuhn bnk...@gmail.com wrote:   but it's invalid to set it to anything other than the two values I just mentioned. That's the part I'd like to see changed.  I understand that if it's present, it's on.  So, why can't async=true be valid?  I think all browser

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Brian Kuhn
I can accept that. It's just a shame that true and false can't be supported for something called a boolean attribute. Anyone have any thoughts on setAttribute vs. setting the attribute directly? My test show that they both work. Thanks, Brian On Dec 8, 2009 1:57 PM, Tab Atkins Jr.

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Garrett Smith
On Tue, Dec 8, 2009 at 1:41 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: On Tue, Dec 8, 2009 at 1:49 PM, Brian Kuhn bnk...@gmail.com wrote: How do I correctly set a boolean attribute on a DOM element object in Javascript? var script = document.createElement('script'); script.async = true;  

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Tab Atkins Jr.
Some clarification is in order; I didn't answer fully and was corrected elsewhere. There are two distinct notions of attributes here. The first, the content attribute, is what you're manipulating when you do foo.setAttribute() or foo.getAttribute(). The second, the IDL attribute (may be called

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Markus Ernst
Tab Atkins Jr. schrieb: On Tue, Dec 8, 2009 at 3:48 PM, Brian Kuhn bnk...@gmail.com wrote: but it's invalid to set it to anything other than the two values I just mentioned. That's the part I'd like to see changed. I understand that if it's present, it's on. So, why can't async=true be

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Thomas Broyer
On Tue, Dec 8, 2009 at 8:49 PM, Brian Kuhn bnk...@gmail.com wrote: How do I correctly set a boolean attribute on a DOM element object in Javascript? var script = document.createElement('script'); script.async = true;        // makes the most sense, but appears go against the spec

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Dean Edwards
On 08/12/2009 23:04, Garrett Smith wrote: Setting an attribute to the empty string may have the effect of removing the attribute in some browsers. Which browsers/properties? -dean

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Garrett Smith
On Tue, Dec 8, 2009 at 4:49 PM, Dean Edwards dean.edwa...@gmail.com wrote: On 08/12/2009 23:04, Garrett Smith wrote: Setting an attribute to the empty string may have the effect of removing the attribute in some browsers. Which browsers/properties? s/removing the attribute/setting a false

Re: [whatwg] boolean attributes in javascript

2009-12-08 Thread Brian Kuhn
Thanks Tab, and everyone else. This has been enlightening! On Tue, Dec 8, 2009 at 3:22 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: Some clarification is in order; I didn't answer fully and was corrected elsewhere. There are two distinct notions of attributes here. The first, the