- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Tue, 7 Jul 2009 13:01:23 +1200
On Tue, Jul 7, 2009 at 12:38 PM, Hans Schmucker <hansschmucker at gmail.com>wrote: > I simply think that when using SVG filters, we are much more likely to > add a lot of these "border-cases" where browsers behave subtly > different. We already have that problem with SVG in general and it's > really holding SVG back. Whatever those issues are that you're referring to, they need to be fixed in SVG already. Creating a new set of "well-defined" behaviours in <canvas> can only add more work. If the new "well-defined" behaviours fail to match the behaviour SVG requires, then the situation will be even worse. (I'd actually like to know what all these SVG filter "border-cases" are. I've discovered a few spec issues and reported them to the SVG list, but not too many. There are certainly browser bugs in some cases, but any new proposal will have browser bugs too.) A lot of functionality offered by SVG filters is > either already included elsewhere in the Canvas spec or simply not > relevant. Like what? Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090707/b38a3d5c/attachment.htm>
Received on Monday, 6 July 2009 18:01:23 UTC