W3C home > Mailing lists > Public > www-style@w3.org > August 2013

Re: [css3-ui] Support cropping in the middle of texts using 'text-overflow'

From: Brad Kemper <brad.kemper@gmail.com>
Date: Sun, 11 Aug 2013 13:47:58 -0700
Cc: Kenneth Auchenberg <kenneth@auchenberg.dk>, www-style list <www-style@w3.org>, "tantek@cs.stanford.edu" <tantek@cs.stanford.edu>, "roc@ocallahan.org" <roc@ocallahan.org>
Message-Id: <1051D6C9-6838-4A80-A130-B0E4A381A9A2@gmail.com>
To: Sebastian Zartner <sebastianzartner@gmail.com>

On Jul 22, 2013, at 3:59 PM, Sebastian Zartner wrote:

> On 20 July 2013 16:51, Brad Kemper <brad.kemper@gmail.com> wrote:
> On Jul 18, 2013, at 3:09 PM, Kenneth Auchenberg <kenneth@auchenberg.dk> wrote:
>> Great initiative to get this much desired functionality speced out .
>> Do we know of similar middle text truncation is implemented in platforms, like Mac OSX? 
>> Would be great with consistency between the web and existing platforms.
>> -
>> Kenneth Auchenberg
>> +45 53 22 22 33
>> On Thu, Jul 18, 2013 at 11:38 PM, Sebastian Zartner <sebastianzartner@gmail.com> wrote:
>> As I already proposed earlier[1] there should be a way to allow truncating text contents in the middle.
>> I was asked to add the current proposal to the W3C wiki to allow further discussion on this. So here it is:
>> http://www.w3.org/wiki/Text-overflow_middle_cropping
>> There are definitely still some unconsidered parts, so it would be great to hear some opinions on this.
>> Sebastian
>> [1] http://lists.w3.org/Archives/Public/www-style/2012Apr/0336.html
> I understand the need for text-overflow-min-width, but I don't really get why we need start, middle, and end values. If text-overflow-min-width is more than zero (1ch, for instance), then the ellipsis or string or clipping would happen in the middle somewhere, and you would not then also want additional ellipsis, strings in other positions (and the clipping would occur as a natural result of where the the one ellipsis or string did go).
> The defintion of text-overflow-min-width is not totally correct yet. What's probably expected is to have either start/end truncation or middle truncation, but not both at the same time.
> I.e. what it should be able to handle is this:
> Whole text:
> This is some truncated text.
> End truncation:
> This is so…
> Start truncation:
> …ated text.

When is this actually needed for text overflow? Can you provide for samples, perhaps from in print or something, where the start of the text is missing, in favor of the end showing?

> Start and end truncation:
> …ome trunca…

That looks pretty odd to me, and not readable.

> Middle truncation:
> This …text.
> For start/end truncation text-overflow-min-width would just need to hold one value, while for middle truncation you may want to define the min. width of the start and end part separately.

That seems like overkill, and would result in more cases where the text is unable to be truncated further. What then? Wouldn't it be better to keep truncating in the middle than to, what, overflow the box on the right, or slice off part of the word on the right because you aren't able to truncate any more according to the min values?

> So it would hold two values. This differentiation is not written down in the wiki page yet.
> I'm open for ideas how to achieve the above.
> Also, I think text-overflow-min-width would need to be more of a suggestion than an absolute, as you would probably want to ensure at least one character at the start, in case the value was larger than the length of the line.
> I believe that should be up to the author. But of course a good default value like e.g. 1ch should be chosen.

If the author's intent is to have middle truncation, then I don't think min values should prevent the browser from doing that smartly once it reaches the extremes.

Received on Sunday, 11 August 2013 20:48:27 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:30 UTC