[whatwg] canvas Firefox support for toDataURL broken

2007-07-10 Thread dev
Hey, I am not sure if this is the correct place to post this, so forgive me if I am wrong (and point it out too). The spec states the toDataURL(image/svg+xml) should return image in svg format , if it can't support that then png image should be returned. But it seems firefox throws an exception

Re: [whatwg] canvas Firefox support for toDataURL broken

2007-07-10 Thread Philip Taylor
On 10/07/07, dev [EMAIL PROTECTED] wrote: Hey, I am not sure if this is the correct place to post this, so forgive me if I am wrong (and point it out too). The spec states the toDataURL(image/svg+xml) should return image in svg format , if it can't support that then png image should be

Re: [whatwg] getElementsByAttr

2007-07-10 Thread Charles McCathieNevile
On Fri, 06 Jul 2007 23:38:37 +0200, Sander [EMAIL PROTECTED] wrote: Dan Dorman schreef: On 7/6/07, Sander [EMAIL PROTECTED] wrote: I haven't read the whole draft yet so maybe it's in there, but can you, or anyone else, explain why there is both a selectElement and a selectAllElements method?

Re: [whatwg] getElementsByClassName

2007-07-10 Thread Dan Dorman
On 7/9/07, Jonas Sicking [EMAIL PROTECTED] wrote: I agree with Simon here. Allowing arrays to be passed in doesn't add any extra value and complicates the implementation significantly. I think that the by far most common case is going to be passing a single class name, so adding multiple ways of

Re: [whatwg] Suggestions on postMessage (6.4, cross-document messaging)

2007-07-10 Thread Aaron Boodman
On 7/10/07, Jeff Walden [EMAIL PROTECTED] wrote: why not instead change the API to |postMessage(message, otherWindow)|, such that sending a message to another window involves getting the other window and calling |postMessage| on *your* window? This is a great idea. We were thinking of