- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 20 Aug 2025 15:09:51 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-overflow-4] `line-clamp` shorthand syntax is ambiguous``, and agreed to the following: * `RESOLVED: Rename block-ellipsis: none to no-ellipsis, make empty string behave the same as it.` <details><summary>The full IRC log of that discussion</summary> <astearns> (folks are convinced by the presentation)<br> <fantasai> andreubotella: [explains slight different between "" and none]<br> <fantasai> fantasai: why not just rename 'none' to 'clip' or something<br> <fantasai> florian: in any case we should handle empty string case better<br> <fantasai> fantasai: block-ellipsis: no-ellipsis<br> <fantasai> andreubotella: we weren't planning to ship the <string> value in the initial rollout<br> <fantasai> andreubotella: but someone is working on text-overflow: <string> so maybe we can do it anyway<br> <fantasai> florian: if there is a string, it needs to insert the string. if the string is empty, insertion of nothing and non-insertion, difference is not deliberate<br> <fantasai> florian: difference now is that when you insert empty string, in some rare cases you delete the whole line<br> <fantasai> andreubotella: block-ellipsis clamps to the last line break opportunity where the ellipsis fits<br> <fantasai> andreubotella: if no line-break opportunities, then you replace the line with the ellipsis<br> <fantasai> florian: that is not deliberate<br> <fantasai> fantasai: still think having a keyword would be nice, even if you are fixing the string<br> <fantasai> ...<br> <fantasai> fantasai: isn't it the initial value?<br> <fantasai> andreubotella: no, but it is the default value when omitted in certain shorthand combinations<br> <fantasai> SebastianZ: my suggestion was to use a new keyword for max-lines, 'unlimited'<br> <fantasai> SebastianZ: because that was the part where 'none' in line-clamp and max-lines clashed<br> <fantasai> SebastianZ: right?<br> <fantasai> andreubotella: -webkit-line-clamp: none still needs to disable clamping<br> <fantasai> andreubotella: though behavior of all browsers is consistent now, used to be weird<br> <fantasai> andreubotella: line-clamp: none doesn't need to map to max-lines: none, but<br> <fantasai> SebastianZ: should introduce new keyword for not clamping, then it woudl solve the issue<br> <fantasai> andreubotella: because clas his between block-ellispsis: none and none<br> <fantasai> fantasai: so, suggest none -> no-ellipsis<br> <fantasai> florian: could just say ""<br> <fantasai> fantasai: but then you have to implement <string><br> <fantasai> florian: yeah<br> <fantasai> fantasai: It's useful to be able to separate that out as a feature<br> <SebastianZ> +1 for no-ellipsis<br> <fantasai> fantasai: there are other implementations than chrome. If <string> is significant work, then don't make it required for basic behavior<br> <fantasai> florian: 'blank' is easier to type than ellipsis<br> <fantasai> SebastianZ: blank could be misinterpreted as a space<br> <fantasai> [nods in sympathy]<br> <fantasai> [more bikeshedding]<br> <oriol> q+<br> <fantasai> Florian points out that Chrome is only now implementing text-overflow: <string>, despite how old the property is<br> <astearns> ack oriol<br> <fantasai> oriol: can say it's a string, but only allow some strings<br> <fantasai> oriol: e.g. grid-template-areas restricts which strings are valid<br> <fantasai> oriol: it's weird, but could be expanded in the future<br> <fantasai> RESOLVED: Rename block-ellipsis: none to no-ellipsis, make empty string behave the same as it.<br> <RRSAgent> I have made the request to generate https://www.w3.org/2025/08/20-css-minutes.html fantasai<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12416#issuecomment-3206816925 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 August 2025 15:09:52 UTC