- From: Aryeh Gregor <Simetrical+w3c@gmail.com>
- Date: Tue, 5 Oct 2010 13:11:51 -0400
- To: Philip Taylor <pjt47@cam.ac.uk>
- Cc: James Graham <jgraham@opera.com>, Anne van Kesteren <annevk@opera.com>, "'public-html-testsuite@w3.org' (public-html-testsuite@w3.org)" <public-html-testsuite@w3.org>, Kris Krueger <krisk@microsoft.com>
On Tue, Oct 5, 2010 at 9:46 AM, Philip Taylor <pjt47@cam.ac.uk> wrote: > Also it assumes the browser supports SVG in <img>, which doesn't seem > reasonable yet. (I think it's only safe to assume PNG, JPEG, GIF, and > animated GIF). It should probably be designed so that it will pass in a > browser that doesn't implement SVG in <img>, and fail only if it does > support in <img> but not in drawImage. If the goal is mainly to test the latest versions of popular browsers, it's safe to assume that SVG is supported in <img>, because as far as I know, the latest versions of all popular browsers support SVG in <img> (Firefox gains support in 4.0, IE in 9.0, WebKit/Opera have had support for a while). If the goal is to also correctly test hypothetical user-agents that might or might not exist, I don't see why you can assume PNG support either, or anything else, since the spec doesn't require it. I don't know why it should be a goal to correctly test old versions of popular browsers. We necessarily exclude some classes of conforming UAs from the tests already, like those that don't support JavaScript, so why not here too?
Received on Tuesday, 5 October 2010 17:12:41 UTC