- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Jun 2024 18:11:49 +0000
- To: public-css-archive@w3.org
frivoal has just created a new issue for https://github.com/w3c/csswg-drafts: == Position of the text-overflow ellipsis == Firefox, in an `overflow:scroll` or `auto` element, places the ellipsis immediately at the end of the line, even if that leaves a bit of extra room between the ellipsis and the text. When you then scroll the element, as the spec requires, more content gets revealed. The combination of these two things is: by pinning the ellipsis to the end of the line, this enables the ellpsis to visibly stays right where it is as you scroll. If you simply scroll (using two fingers on trackpad, the mouse's scrollwheel, or the scrollbar), that's not immediately visible, because Firefox will hide the ellipsis while you scroll, only to show it again once you release, but if you trigger the scrolling either programatically, or scroll by selecting, then you can see the ellipsis stay put while the rest moves. Currently, neither Chrome nor Safari will reveal more content as you scroll, and instead they scroll the ellipsis with the text, revealing blank space. That in itself is a spec violation, but that's another story. You can try this here (using Firefox): http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=12804 As long as you reveal more content as you scroll, which you should, I think the Firefox behavior is nice, but that placement of the ellipsis is a spec violation, because the spec says that you must: > place the ellipsis/string immediately adjacent to the applicable edge(s) of the remaining inline content. How about we relax that requirement, and instead spec one of the two following options: * the ellipsis must be placed somewhere between the edge of the remaining inline content and the edge of the box, with the exact placement within that space being up to the UA * the ellipsis must be placed either at the edge of the remaining inline content or the edge of the box, at the UA's discretion Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10418 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 June 2024 18:11:54 UTC