W3C home > Mailing lists > Public > www-style@w3.org > January 2009

Re: [css3-values] new editor's draft (and [css3-box])

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 20 Jan 2009 21:07:00 +1300
Message-ID: <11e306600901200007m7687015cv16b8cabfa3077822@mail.gmail.com>
To: "Alex Mogilevsky" <alexmog@microsoft.com>
Cc: "David Hyatt" <hyatt@apple.com>, "Håkon Wium Lie" <howcome@opera.com>, "Christoph Päper" <christoph.paeper@crissov.de>, "www-style@w3.org" <www-style@w3.org>
On Tue, Jan 20, 2009 at 7:14 PM, Alex Mogilevsky <alexmog@microsoft.com>wrote:

>  Actually this wouldn't handle the target scenario of never scaling an
> image on client. Being a perfectionist photographer who wants to make sure
> any image scaling is done by the most advanced software, I would still be
> forced to write script that makes sure image size in device pixels is the
> perfect match to intrinsic size.
> **

That goal is incompatible with smooth zooming to arbitrary scales, and
adhering to it would be a disaster for media whose resolutions the author
hasn't provided for in advance*. Plus I've never heard anyone express this
desire before. So I feel comfortable ignoring this requirement.

* Unless by "script" you mean using a high-performance JS engine and HTML5
<canvas> to rescale your image on the client using your preferred algorithm.
That would be cool.

"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
Received on Tuesday, 20 January 2009 08:07:35 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:23 UTC