[csswg-drafts] [css-anchor-position] Was changing acceptable element algorithm intentional? (#11170)

anttijk has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-anchor-position] Was changing acceptable element algorithm intentional? ==
https://github.com/w3c/csswg-drafts/commit/fe8e40d37faae "Rewrite the ordering conditions on 'acceptable anchor element' to be more explicit and hopefully clearer" actually changed the algorithm somewhat. Specifically in the "different containing blocks" case the tree order of the elements no longer matters. This affects for example

http://wpt.live/css/css-anchor-position/anchor-name-002.html (the first target now gets anchored)
http://wpt.live/css/css-anchor-position/anchor-scroll-002.html (all targets attach to the last anchor)

The commit message indicated that the intention was to clarify the algorithm so I'm wondering if the behavior changes were intentional?



Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11170 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 8 November 2024 12:39:21 UTC