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

[csswg-drafts] Allowing (or not) alternate ellipsis behavior for block-overflow

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Jul 2018 09:24:58 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-340161259-1531301096-sysbot+gh@w3.org>
frivoal has just created a new issue for https://github.com/w3c/csswg-drafts:

== Allowing (or not) alternate ellipsis behavior for block-overflow ==
The spec says:
> If there is no next fragmentation container and thus the remainder of the content after the break would be discarded, then the UA may visually replace the contents of the line, as it does for text-overflow.

in https://github.com/w3c/csswg-drafts/issues/390#issuecomment-372143424, Mats Palmgren said:

> I think this "may" should be changed to a "must", or alternatively, the entire sentence be removed. I don't see any upsides to allowing UAs to have incompatible behavior for this common case.

The idea was that the behavior allowed by this "may" sentence was worse, and that we wanted browsers to do the full thing, but that it was more involved, and that doing it as a visual replacement was a tolerable approximation (only in the case of no subsequent fragmentainer).

If implementors are OK with going with the full thing, I'd be happy about deleting that.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2905 using your GitHub account
Received on Wednesday, 11 July 2018 09:25:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 July 2018 09:25:48 UTC