Re: [csswg-drafts] [css-overflow] convert -webkit-line-clamp alias requirement into a spec issue (#2847)

The CSS Working Group just discussed `convert -webkit-line-clamp alias requirement into a spec issue`, and agreed to the following:

* `RESOLVED: Accept adding -webkit-discard value to continue prop to rep line-clamp that only applies to webkit flex boxes and makeit shorthand expansion for -webkit-line-clamp`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: convert -webkit-line-clamp alias requirement into a spec issue<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2847<br>
&lt;dael> florian: Talked at F2F. Had follow up meeting afterwards.<br>
&lt;dael> florian: We went through what was needed for supporting webkit-line-clamp in contrast with spec. Concludedcan't be a straight alias because there are quirks we don't want to prop.<br>
&lt;florian> https://github.com/w3c/csswg-drafts/commit/2cc319448f4732c127fa43213ce7cf7d96de04ac<br>
&lt;dael> florian: Defined ashorthanding mech, added to the spec to the satisfaction of all present.<br>
&lt;dael> florian: Commit ^<br>
&lt;dael> florian: Given non-prefixed line-clamp works for some properties the prefixed version also would but setting weird values for weird behavior. Other than necessary bits it's all same.<br>
&lt;dael> florian: I think people who cared were in the room and agreed, but if anyone else wants to say something...<br>
&lt;dael> AmeliaBR: You could explain all the weirdness in terms of longhand it's just that prefix sets different defaults compared to regular version?<br>
&lt;dael> florian: Most are normal, but the one that takes discard takes a new webkit-discard value<br>
&lt;dael> fantasai: There's a lot of weirdness in webkit-line-clamp and spec makes most of the weird go away. There's one that would not be web compat where line-clamp is all boxes and webkit-line-clamp applies to old style flex container and prop to flex items. That's a little weird. Other differences between spec and webkit like where ellipsis goes we don't think are issues<br>
&lt;dael> fantasai: This is because they're prob people are complaining about and working around already<br>
&lt;dael> Rossen_: Okay. not because there will be no issues for rendering but b/c people expect better behavior so expectation people will adapt<br>
&lt;dael> fantasai: Expectation is it won't cause pages to break in major ways<br>
&lt;dael> florian: Small differences that are mostly improvements<br>
&lt;dael> Rossen_: Iwould only worry if changing line height in significant way. Some sites with tight layout like news sites they produce containers that have weirdoverlap and looks odd with as little as 1px line height difference<br>
&lt;dael> Rossen_: If this is mostly an improvement we'll have to see how it goes<br>
&lt;dael> florian: Moz has looked and to the extent they found sites using it this won't be a problem. Won't know for sure until we try.<br>
&lt;dael> Rossen_: I think overall approach and alignment between legacy and new sounds great<br>
&lt;dael> Rossen_: Any additional thoughts or feedback before we resolve to move forward with proposal in https://github.com/w3c/csswg-drafts/commit/2cc319448f4732c127fa43213ce7cf7d96de04ac ?<br>
&lt;dael> Rossen_: florian what is summary of resolution?<br>
&lt;dael> florian: Accept the edit that's in the spec.<br>
&lt;dael> fantasai: Accept adding -webkit-discard value to continue prop to rep line clamp that only applies to webkit line boxes and makeit shorthand expansion for webkit lineclamp<br>
&lt;fantasai> s/line clamp/line-clamp/<br>
&lt;fantasai> s/line boxes/flex boxes/<br>
&lt;fantasai> s/webkit lineclamp/-webkit-line-clamp/<br>
&lt;dael> RESOLVED: Accept adding -webkit-discard value to continue prop to rep line-clamp that only applies to webkit flex boxes and makeit shorthand expansion for -webkit-line-clamp<br>
&lt;dael> TopicL  Allowing (or not) alternate ellipsis behavior for block-overflow<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2847#issuecomment-474918325 using your GitHub account

Received on Wednesday, 20 March 2019 16:35:04 UTC