- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Nov 2021 00:04:57 +0000
- To: public-css-archive@w3.org
emilio has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-scroll-anchoring] Consider invalidating anchor after adjustment if at the point of selection the anchor has dirty descendants == See https://bugzilla.mozilla.org/show_bug.cgi?id=1738781 for context. At first I thought that the test-case there behaving suboptimally was a Firefox bug, but after more investigation I think it's a Chromium bug instead (see https://bugzilla.mozilla.org/show_bug.cgi?id=1738781#c2 and following). I think we could consider invalidating the anchor after applying an adjustment if when we selected the anchor there were dirty children. This will guarantee a better anchor regardless of focus moving or what not. Blink implements something like that already for `content-visibility: auto`. cc @chrishtr @vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6787 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 November 2021 00:05:01 UTC