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

Re: [CSS3-UI] text-overflow:ellipsis (freshly rewritten/expanded and incorporated into editor's draft)

From: Tantek Çelik <tantek@cs.stanford.edu>
Date: Tue, 25 Jan 2011 23:27:12 -0800
Message-ID: <AANLkTi=4JkONi=ZndDpLWzu7gRa6R=q0wed=XKyNZ-SA@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: robert@ocallahan.org, www-style@w3.org
Out of order replies as issues are resolved.

On Sun, Jan 23, 2011 at 20:11, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 1/23/11 10:04 PM, Robert O'Callahan wrote:
>>
>> On Mon, Jan 24, 2011 at 8:02 AM, Tantek Çelik <tantek@cs.stanford.edu
>> <mailto:tantek@cs.stanford.edu>> wrote:
>>    If that's so, then web authors/developers are unlikely to be depending
>>    on things other than "the simplest situations".
>
>>
>>
>> The behavior of
>> text-overflow:ellipsis on lines containing right-to-left text is
>> currently undefined.
>
> This.  Web authors/developers writing in _English_ are unlikely to be
> depending on things other than "the simplest situations".
>
> Anyone writing in an RTL language is just screwed, as things stand. It's not
> clear to me quite why this is OK for a W3C spec...

It's not.

I've updated the editor's draft to provided a clearer description of
how direction/ltr/rtl interact with text-overflow ellipsis (as well as
provided some simple rendering examples), consistent with current
Opera and WebKit implementations.

http://dev.w3.org/csswg/css3-ui/#text-overflow

Thanks,

Tantek

-- 
http://tantek.com/ - I made an HTML5 tutorial! http://tantek.com/html5
Received on Wednesday, 26 January 2011 07:28:26 GMT

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