Re: [csswg-drafts] [css-overflow] Consider support for multiple-line ellipsis

> I'd suggest "The rendering is unaffected." instead.

done: https://github.com/w3c/csswg-drafts/commit/9e6c64e311ae1dea3822a8d7d0e0d06533a50ef9

> I think this "may" should be changed to a "must", or alternatively, the entire sentence be removed.

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 quite a bit 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.

> Does the inserted text affect `::first-letter`/`::first-line` in any way?

If it is in the first lines (e.g. `max-lines:1`), then it should take the styles that affect the first line. Otherwise, we'll get weird and inconsistent typography in the first line. I believe that is already a consequence of "placed [...] as a direct child of the block container’s root inline box", but it doesn't hurt to say so if we agree (or to argue it out and then spec it if we don't).

For `::first-letter`, I am less sure. I'm not what sure what the use case would be, and neither of what the implementation complexity would be. Any suggestion?

> >   The means of breaking any resulting cycles is up to the UA.
> Again, vague spec text[...]. I'd prefer the spec to say something concrete [...].

Fair enough. This may be a sufficiently involved question on its own to deserve it's own issue.

> > If the block overflow ellipsis is too long to fit in the line, the result is undefined.
> this is too lenient IMO

I suspect there's a significant difference in implementation complexity between treating as an unbreakable string that overflows and climbing back up the previous lines. I suppose we could start by specifying it as unbreakable string that overflows, and later expose a pseudo element to let people switch to different behavior(s?) by applying some style. But this is a point where I'd be most interested to hear author / designer / evangelist feedback.

-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/390#issuecomment-372160977 using your GitHub account

Received on Sunday, 11 March 2018 23:51:35 UTC