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

Re: [CSS21] 11.1.2: 'clip': various issues

From: fantasai <fantasai.lists@inkedblade.net>
Date: Thu, 03 Mar 2011 18:21:59 -0800
Message-ID: <4D704CC7.6090006@inkedblade.net>
To: Peter Moulder <peter.moulder@monash.edu>, www-style@w3.org
On 09/24/2010 05:56 AM, Peter Moulder wrote:
> My apologies, there was an error in the test case.  The revised implementation
> results are that most browsers seem to ignore the 'direction' property of the
> element with 'clip' as far as how the 'clip' coordinates are interpreted.
>
> (I also tried setting direction:rtl on the root element in case any browsers
> were testing an ancestor; but I didn't check this variation for all browsers.
> I didn't check any other possible interpretations of "in right-to-left text".)
>
> Konqueror was the only one where I found rtl making a difference to 'clip'
> coordinates.  It apparently tests the 'direction' property of the element that
> has 'clip', and (in the rtl case) positive offset means farther to the left,
> i.e. the behaviour that I considered more desirable rather than the behaviour
> that I considered the best reading of the text.

I believe this issue was addressed as CSS2.1 Issue 220:
   http://wiki.csswg.org/spec/css2.1#issue-220

> I also note that visuren.html#propdef-direction appears to be trying to give a
> complete list of the effects of the 'direction' property, but the list seems to
> omit 'clip', resolution of border conflicts with collapsed table border model,
> which margin is ignored (10.3), and probably other things (search for
> propdef-direction).  I suggest either adding to its list of effects, or making
> it clearer that it's not a complete list.

I've filed this as CSS2.1 Issue 235:
   http://wiki.csswg.org/spec/css2.1#issue-235

~fantasai
Received on Friday, 4 March 2011 02:22:37 GMT

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