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

RE: FW: NoWrap property [CSS2.1] [css3-text]

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Mon, 8 Dec 2008 20:55:10 -0800
To: fantasai <fantasai.lists@inkedblade.net>
CC: "robert@ocallahan.org" <robert@ocallahan.org>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <7C2F64B551D8664AAD94A28DAC37D0206B5068E8F8@NA-EXMSG-C103.redmond.corp.microsoft.com>
I think you are right - that is about whitespace collapsing, not actually nowrap. It helps to define why collapsed whitespace may create a break.

I am still somewhat concerned with saying "When wrapping, line breaking opportunities are determined based on the text prior to the white space collapsing steps above.". Maybe it is irrational, but it is a much broader statement than Robert's reasoning, I am not sure what other effects it could create.

-----Original Message-----
From: fantasai [mailto:fantasai.lists@inkedblade.net]
Sent: Monday, December 08, 2008 7:53 PM
To: Alex Mogilevsky
Cc: robert@ocallahan.org; www-style@w3.org
Subject: Re: FW: NoWrap property [CSS2.1] [css3-text]

Alex Mogilevsky wrote:
> Although you seem to agree with Robert's reasoning, the proposed
> change is different from Firefox behavior (as described by Robert).
>
> The proposed change will allow a break between x and y here
>
>         x<nowrap> </nowrap>y
>
> While Firefox implementation and reasoning does not.

Actually, if you take roc's explanation that a break at a space is
considered to be *at* the space (i.e. inside it) and not before or
after the space character, then it's consistent. Basically a space
is treated like two characters with a breakpoint in between. Given
that interpretation, wrapping <nowrap> around a space then gives
the &nbsp; behavior.

~fantasai

Received on Tuesday, 9 December 2008 04:55:51 GMT

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