W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2018

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

From: Cameron McCormack via GitHub <sysbot+gh@w3.org>
Date: Sat, 30 Jun 2018 01:58:21 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-401509864-1530323900-sysbot+gh@w3.org>
I think it depends what `display: -webkit-box;` really means.

Per spec, without it, I would expect all three sub-tests to render the same, with an ellipsis after the "3" and all subsequent lines fragmented away.  This is because the `max-lines` applies to the parent div, and the child div's lines are in the same block formatting context as the parent's.

But if you interpret `display: -webkit-box;` as being like creating a flex item, then that does establish an independent formatting context.  In that case I would expect the first two sub-tests to be the same as before (ellipsis after "3"), but the third sub-test would look like it does in Chrome now, i.e. no ellipsis and no lines fragmented away, since the container div only generates two line boxes in its block formatting context (the "1" and the "7").

GitHub Notification of comment by heycam
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2847#issuecomment-401509864 using your GitHub account
Received on Saturday, 30 June 2018 01:58:25 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 30 June 2018 01:58:26 UTC