W3C home > Mailing lists > Public > www-style@w3.org > July 2011

Re: [css3-images] Features Overview

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 7 Jul 2011 12:01:54 -0700
Message-ID: <CAAWBYDAn6cVxxSdsOQPs5YbCehBJ0pEnVnvoKHQCgrP57OTR8Q@mail.gmail.com>
To: Yves Lafon <ylafon@w3.org>
Cc: Raphaël Troncy <raphael.troncy@eurecom.fr>, fantasai <fantasai.lists@inkedblade.net>, www-style@w3.org, public-media-fragment@w3.org
On Thu, Jul 7, 2011 at 12:51 AM, Yves Lafon <ylafon@w3.org> wrote:
> On Wed, 6 Jul 2011, Tab Atkins Jr. wrote:
>> 2011/7/6 Raphaël Troncy <raphael.troncy@eurecom.fr>:
>>> Following these
>>> discussions, we have added the following sentence to the spec:
>>>
>>> "Note that in the case of pixel-based clipping areas, application of
>>> those
>>> areas to multi-resolutions visual media is undefined."
>>>
>>> in the section 4.2.2 [2].
>>
>> What's the reasoning for making it undefined?  If it's just "it's
>> hard", then I don't find that acceptable.
>
> For percent-based clipping fragments, it makes sense at all resolutions (but
> perhaps having them integer-based is sub-optimal in many cases), but for
> pixel-based ones, it is impossible to know the intent.
> Does the format as a "default" version to apply the pixel clipping to? the
> first one? last one? bigger one? The one that fit the display?
> So it's not that it's hard, I just don't see how this could work reliably.

I agree that it's difficult to find a good answer.  If we think the
problem is essentially impossible, then we should just make it
explicitly unsupported, not undefined.

~TJ
Received on Thursday, 7 July 2011 19:02:41 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:42 GMT