[whatwg] canvas Firefox support for toDataURL broken
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 to canvas.toDataURL(image/svg+xml) whereas it should be returning the image in png format. I know many firefox devels monitor this list, so I thought might as well post it here. Sorry if I was wrong. Regards, dev
Re: [whatwg] canvas Firefox support for toDataURL broken
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 returned. But it seems firefox throws an exception to canvas.toDataURL(image/svg+xml) whereas it should be returning the image in png format. That's correct, and it's just a bug in Firefox. Throwing an exception on toDataURL(image/png, null) is a vaguely similar bug. (Opera agrees with the spec in both cases. Safari doesn't implement toDataURL at all). Probably Firefox should change its behaviour, unless it has good reasons not to, in which case possibly the spec should change to match it. https://bugzilla.mozilla.org/ is the best place for reporting bugs like this, under component 'Core' / 'Layout: Canvas'. (I've got a load of test failures recorded at http://canvex.lazyilluminati.com/tests/tests/results.html, and more from not-quite-finished tests - I've been waiting to have more completeness before reporting all the found bugs, but I keep getting distracted by other things and haven't got around to that yet...) Regards, dev -- Philip Taylor [EMAIL PROTECTED]
Re: [whatwg] getElementsByAttr
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? ... If you know you're after one element, you get to deal with it directly rather than first referencing the only contents of a single-element array. But document.selectAllElements(#first)[0] would do the trick. The working group recognises that this is not necessarily critical either way, but decided on having the single element method as an optimisation that does something reasonably useful (in our opinion) for both the implementors of user agents and the authors of code. It is listed as issue 110 in the WebAPI group issue tracker. Cheers Chaals -- Charles McCathieNevile, Opera Software: Standards Group hablo español - je parle français - jeg lærer norsk [EMAIL PROTECTED]Catch up: Speed Dial http://opera.com
Re: [whatwg] getElementsByClassName
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 passing multiple class names seems like overkill. Granted, the most common case will indeed be asking for a single class name. But, if we're going to the trouble of accepting multiple class names, it seems shortsighted to restrict the parameter for the multi-class case to a space-separated string, which is really just a kludgey way of representing a list (or array). Dan
Re: [whatwg] Suggestions on postMessage (6.4, cross-document messaging)
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 implementing PostMessage in Gears and it would be much easier if that were the API. - a
