W3C home > Mailing lists > Public > www-style@w3.org > December 2008

Re: FW: NoWrap property

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 08 Dec 2008 14:27:42 -0800
Message-ID: <493D9F5E.9050601@inkedblade.net>
To: "www-style@w3.org" <www-style@w3.org>

fantasai wrote:
> 
> Robert O'Callahan wrote:
>> In Gecko we follow two principles:
>> 1) Break opportunities induced by white space are entirely governed by 
>>    the value of the 'white-space' property on the enclosing element. 
>> So,    spaces that are white-space:nowrap never create break 
>> opportunities.
>> But
>> 2) When a break opportunity exists between two non-white-space    
>> characters, e.g. between two Kanji characters, we consult the value of 
>>    'white-space' for the nearest common ancestor element of the two    
>> characters to decide if the break is allowed.
>>
>> I think these principles are reasonably intuitive and useful.
> 
> I agree with these.
> 
>> The first principle explains our rendering of your testcases. In your 
>> third testcase, the space after the nowrap span is collapsed away but 
>> we still allow it to create a linebreak opportunity, since it's 
>> white-space:normal.
> 
> This is something that's not clear in the spec: does removed whitespace still
> create a break opportunity? It would be good to discuss this in the context
> of what we want for CSS3. E.g. suppose there is a 'discard' value for white
> space.

I've logged this as issue 91:
   http://wiki.csswg.org/spec/css2.1#issue-91

And for CSS3, ISSUE-75
   http://www.w3.org/Style/CSS/Tracker/issues/75

~fantasai
Received on Monday, 8 December 2008 22:28:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:17 GMT