- From: DavidJCobb via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Dec 2022 22:29:11 +0000
- To: public-css-archive@w3.org
`clip-path` is unsuitable for other reasons as well. I recently got subpixel rounding errors that caused a browser (don't recall whether it was Firefox or Chrome) to clip a 1px border off of an element, even though that border should have fallen within the specified path. It's incredibly unfortunate that setting `overflow-x: auto` on an ancestor causes `position: sticky; top: 0` to become locked to that ancestor's always-zero scroll Y-position. -- GitHub Notification of comment by DavidJCobb Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/865#issuecomment-1365490283 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 December 2022 22:29:13 UTC