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 18:17:19 -0800
To: fantasai <fantasai.lists@inkedblade.net>, "robert@ocallahan.org" <robert@ocallahan.org>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <7C2F64B551D8664AAD94A28DAC37D0206B5068E8B9@NA-EXMSG-C103.redmond.corp.microsoft.com>
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.

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

Makes sense to me. How about appending to this paragraph in 2.1:

   # Then, the entire block is rendered. Inlines are laid out, taking bidi
   # reordering into account, and wrapping as specified by the 'white-space'
   # property.

the following:

   | When wrapping, line breaking opportunities are determined based
   | on the text prior to the white space collapsing steps above.

We'd have to make the equivalent changes to CSS3 Text, of course.
(Or possibly only to CSS3 Text, leaving this undefined for CSS2.1.)


Received on Tuesday, 9 December 2008 02:18:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:42 UTC