- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Mon, 7 Feb 2011 16:33:36 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>, Lech <unattended@gmail.com>
- CC: "www-style@w3.org" <www-style@w3.org>
> -----Original Message----- > I don't believe there's a good reason to specify an explicit algorithm. > When you know precisely what algorithm you want, you can implement that > yourself easily in canvas. When you don't care all that much (which > should be the common case), you can just declare your intent and let the > browser do what it wants to make everything look as good as possible. If the answer for your average web author is 'code your image scaling algorithm yourself' then I would most definitely argue there is a good reason for this ! That is not something the kind of JS code browsers should spend cycles running on a routine basis. (The implied claim that this can 'easily' be done also begs the question: for whom ? And even then, so what ? It's easy to make progress bars and sliders but those are built in HTML5) So the question imo is: why would this be something authors would want to control on a routine basis ?
Received on Monday, 7 February 2011 16:34:14 UTC