- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 May 2025 00:05:56 +0000
- To: public-css-archive@w3.org
Right. So just to confirm, so I can edit accordingly: in the section where we talk about handling scroll at recaluculation points, we also say that we pay attention to transforms, and use the transform bounding box of the anchor (in the coordinate space of the positioned element's containing block) instead of the anchor's actual box. I note this does interact a bit with the request to use different boxes from the anchor (right now we always use the anchor's border box edge). Not sure how we'd handle using padding/content box, unless maybe by applying the same transforms to that reduced box and then finding the bounding box of *that*. Anyway, something to solve for later; paying attention to transforms on the anchor is definitely more important than caring about the content box of an anchor. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8584#issuecomment-2899540643 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 May 2025 00:05:57 UTC