W3C home > Mailing lists > Public > www-style@w3.org > March 2015

Re: Text Overflow With ...

From: Florian Rivoal <florian@rivoal.net>
Date: Tue, 10 Mar 2015 22:18:05 +0100
Cc: ACJ <ego@acjs.net>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <6C30E269-2224-432D-90B5-7A0D1D81F1C0@rivoal.net>
To: Greg Whitworth <gwhit@microsoft.com>

> On 10 Mar 2015, at 18:42, Greg Whitworth <gwhit@microsoft.com> wrote:
> Simon Ferndriger schreef op 4-3-2015 om 13:40:
>> A really great CSS enhancement would be, if I could tell a specific 
>> tag, to cut the containing text to its maximal width and add 3 dots at 
>> the end.
>> [...]
>> if I could set the following CSS:
>> var {
>>  text-overflow:cut;
>>  text-overflow-after:'...';
>>  /* or any similar syntax */
>> }
>> Sounds like something that can currently be achieved with http://dev.w3.org/csswg/css-ui-3/#propdef-text-overflow (with a max-width and perhaps display:inline-blck).

> Yes, this is actually a major undertaking that Florian (added in the To line) is trying to tackle. It isn't just about adding an ellipse or being able to control what content is visible but also the event model and how to fragment this properly. I do believe that the overflow and the fragment specs are the best ones to pay attention to regarding these changes, is that correct Florian?

"text-overflow: ellipsis" (combined with width/max-width and if relevant display:inline-block) can already handle some of the cases. I'd need to see a bit more detail on the example suggested above to see if that's already solvable or not, as it is not entirely clear to me what what attempted.

But you're right Greg that the css-overflow spec [1] is where I'll be landing things to tackle the generalized problem. I've started working on isolating the fragmentation mechanisms: http://dev.w3.org/csswg/css-overflow/#fragmentation

- Florian

[1] http://dev.w3.org/csswg/css-overflow/
Received on Tuesday, 10 March 2015 21:18:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:52 UTC