- From: Aapo Alasuutari via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Dec 2023 08:33:07 +0000
- To: public-css-archive@w3.org
aapoalas has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-position] Popover positioning within a transformed anchor stacking context == In the `anchor()` Function (https://drafts.csswg.org/css-anchor-position-1/#funcdef-anchor) transforms are mentioned with regards to the snapshotted scroll offset of the positioned element. It seems to, however, be unclear if ancestor transforms are to be taken into account for the scroll offset. In concrete terms, at present Chrome's implementation does not seem to take at least parent scale into account when calculating the position of the popover. As a result if an ancestor element has any scale values then the popover element in Chrome starts drifting out of position:  Here a common ancestor of the popup element (top left) and the button (right side, "Bypass") has `transform: translate(223.136px, 0.014px) scaleX(1.85304) scaleY(1.85304)` applied on it, leading to the popover being misplaced. This may be just an implementation bug but on the other hand the spec doesn't exactly spell out what should be the resulting popover position in this case either. Another related fun consideration is of course rotations, though at the end it all should just boil down to the same affine transformations I presume. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9705 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 December 2023 08:33:09 UTC