- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Apr 2024 15:19:31 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-4] Ellipsizing of text in middle of string`, and agreed to the following:
* `RESOLVED: Start work on middle ellipsis in css-overflow-4`
<details><summary>The full IRC log of that discussion</summary>
<fantasai> astearns: are we going to do this, or punt it?<br>
<fantasai> SebastianZ: Longstanding thing I proposed 10 years ago, a way to crop content of an element in the middle instead of at the beginning or end<br>
<fantasai> ... proposal went through some iterations<br>
<fantasai> ... current idea is to make text-overflow a shorthand and introduce text-overflow-handling and text-overflow-position<br>
<SebastianZ> https://github.com/w3c/csswg-drafts/issues/3937#issuecomment-1624382903<br>
<fantasai> text-overflow = <'text-overflow-handling'> || <'text-overflow-position'><br>
<fantasai> text-overflow-handling = auto | [ clip | ellipsis | <string> | fade | <fade()> ]{1,2}<br>
<fantasai> text-overflow-position = [ start || end ] | middle<br>
<fantasai> SebastianZ: we cover the current behaviors, plus cropping<br>
<fantasai> SebastianZ: also outlined rudimentary algorithm later on<br>
<florian_irc> q+<br>
<kizu> q+<br>
<fantasai> SebastianZ: anyone on the call have comments?<br>
<astearns> ack florian_irc<br>
<fantasai> florian_irc: my main concern here is the handling of bidi<br>
<fantasai> florian_irc: in general, just like in start/end of line, should do visual cropping not logical<br>
<fantasai> ... logical cropping is going to be having some strange cropping<br>
<fantasai> s/cropping/questions/<br>
<fantasai> ... in generalized case, including bidi, makes me worry<br>
<fantasai> ... because when you chop start/end, clear what happens, but if you crop middle you have to move the other parts<br>
<fantasai> ... suspect it's more complex than we wish<br>
<astearns> ack kizu<br>
<fantasai> kizu: I don't have any opinion on bidi, but ellipsing in the middle is something I've wanted for more than 10 years<br>
<jfkthame> q+<br>
<fantasai> kizu: Last time, there was concern about not allowing clipping in the middle<br>
<fantasai> kizu: but still good way to do it, if it's exactly in the middle then author can position something interesting there<br>
<fantasai> kizu: but this will require browser to know<br>
<fantasai> kizu: other than that, lots of people want this<br>
<fantasai> kizu: idk if in this issue or other, if we need an ellipsis in multiline<br>
<fantasai> kizu: in our product we need this, but should discuss separately<br>
<fantasai> kizu: but for single-line, a lot of use cases<br>
<astearns> ack jfkthame<br>
<fantasai> jfkthame: I still disagree with Florian that visual ellipsizing in the middle is the right approach for bidi<br>
<fantasai> jfkthame: in most cases, the most important content will be the beginning of the text and/or the end of the text logically speaking<br>
<fantasai> jfkthame: so those pieces should be preserved<br>
<fantasai> jfkthame: I wonder if, given the complexity/uncertainty, is define middle as a feature but leave the behavior of bidi cases for browsers to experiment with initially<br>
<dbaron> Scribe+<br>
<fantasai> jfkthame: until we see what works in real-world use case<br>
<astearns> ack fantasai<br>
<SebastianZ> +1 to what Jonathan said.<br>
<dbaron> fantasai: I ithnk this makes sense -- the question is whether there's implementor interest. If so, we should spec it.<br>
<dbaron> s/ithnk/think/<br>
<dbaron> astearns: do you want to gate specifying on implementor interest? Or should we start it, mark it at risk, and work on spec in parallel?<br>
<fantasai> astearns: should we gate spec on implementer interest?<br>
<fantasai> florian_irc: in this case, I think yes<br>
<fantasai> florian_irc: we agree that this is hard, and we don't know enough to spec it<br>
<fantasai> florian_irc: so even if we did spec it, we wouldn't be able to get interop-level detail<br>
<fantasai> astearns: even if there's open questions, the majority of use cases aren't bidi<br>
<andreubotella> q+<br>
<fantasai> astearns: it's something devs need and have a use for<br>
<florian_irc> q+<br>
<astearns> ack andreubotella<br>
<fantasai> andreubotella: Chromium has an implementation of ellipsis in the middle that they use for file selection<br>
<fantasai> andreubotella: I don't know what it does wrt bidi, but they have an implementation<br>
<astearns> ack florian_irc<br>
<fantasai> florian_irc: even if not bidi, there's still ambiguity wrt visual or logical middle<br>
<fantasai> florian_irc: if non-monospace font, where is the middle?<br>
<fantasai> florian_irc: effect of disagreeing will be less dramatic, but still will have disagreement<br>
<SebastianZ> q+<br>
<fantasai> florian_irc: but maybe useful enough to spec<br>
<fantasai> florian_irc: would prefer to wait until interest, but not an objection<br>
<astearns> ack SebastianZ<br>
<fantasai> SebastianZ: There was at some point an implementation in XUL<br>
<fantasai> SebastianZ: but they removed it at some point<br>
<fantasai> dholbert: we replaced it with another hack based on HTML+CSS<br>
<astearns> ack SebastianZ<br>
<fantasai> dholbert: we have something, but idk how good it is. Similar to Chromium<br>
<fantasai> astearns: given that there does appear to be something implemented, is that enough?<br>
<fantasai> fantasai: can't speak for Apple, but doubt we'd object<br>
<fantasai> jfkthame: unsure when we'd get to it, but some interest<br>
<fantasai> jfkthame: we know that what we've got doesn't handle i18n well<br>
<fantasai> jfkthame: and partly lack of a spec has discouraged us from being more thorough about integrating with CSS<br>
<fantasai> astearns: I'm inclined to resolve that we start the spec of this, knowing it will be complicated, and it may take awhile<br>
<fantasai> florian_irc: Do we start with SebastianZ's proposal of two longhands?<br>
<fantasai> astearns: seems like a good place to start<br>
<fantasai> fantasai: probably need to bikeshed -handling at some point<br>
<fantasai> astearns: proposed to start?<br>
<fantasai> RESOLVED: Start work on middle ellipsis in css-overflow-4<br>
</details>
--
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3937#issuecomment-2075200210 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 April 2024 15:19:31 UTC