- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Dec 2017 02:05:57 +0000
- To: public-css-archive@w3.org
>From the spec: L3: > [...] must hide characters [...] at the end edge of the line [...] L4: > [...] must hide characters [...] at the applicable edge(s) of the line [...] and > Ellipsing only affects rendering and must not affect layout So old-Blink and Gecko are doing the correct thing here. Also, UAs are supposed to (RFC2119 SHOULD) reveal more content when you scroll. This seems awkward to do with `abcdef CBA...`. As you scroll, you'd presumably get something like this ``` abcdef CBA… bcdef DCBA… cdef FEDCBA ``` which doesn't really feel like scrolling, since the right edge doesn't move. Compare with this what you get in Firefox on [your example (changed from `overflow:hidden` to `overflow:auto`)](http://jsbin.com/kirosinuwo/edit?html,output) >From an i18n point of view, the placement of the ellipsis to the right CBA is also weird. I think `abcdef FED...` makes sense since the ellipsis indicates that the rightmost part of the line was cut, and possibly `abcdef ...CBA` as well since it indicates that the middle of the line was cut (from a UI point of view it makes less sense), but `abcdef CBA...` is just weird : the missing part is (visually) between f and C but the ellipsis is shown next to A, which is confusing. So again, in conclusion, old-Blink and Gecko are doing the correct thing here, and the other browsers should be fixed. Can you file the bug on Blink/layout-NG if there isn't one already? I'll fine the bug on everyone else. We hadn't caught that scenario in the test suite, so I've just [made a new test for it](https://github.com/w3c/web-platform-tests/pull/87809). Review appreciated. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2125#issuecomment-353504368 using your GitHub account
Received on Friday, 22 December 2017 02:06:00 UTC