- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Feb 2025 18:47:18 +0000
- To: public-css-archive@w3.org
For 1, good question. The spec mainly just wants to avoid accidental inline overflow, since the ellipsis string isn't allowed to break. Block overflow isn't as much of a problem, tho. I suspect that we *don't* want to do any special clipping in the block axis. To me, it looks odd that Moz is clipping it to, I guess, within the line box? The other details are all, generally, "like it was the last inline content in the block". Are there specific details of the rendering that you're concerned aren't well-defined by that, or that give bad behavior if you treat it like that? For 2, this shouldn't be any more troublesome than animating 'content' on a ::before pseudo-element, which is currently allowed. I don't immediately see any reason to restrict it. If the author does something particularly weird, that's their fault. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11683#issuecomment-2682970534 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 February 2025 18:47:19 UTC