- From: Ryan Hunt via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Jan 2019 18:48:53 +0000
- To: public-css-archive@w3.org
eqrion has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-scroll-anchoring-1] Anchor node selection algorithm should specify how inline elements are traversed == The [anchor node selection](https://drafts.csswg.org/css-scroll-anchoring-1/#anchor-node-selection) section specifies that: ``` The anchor node is either a non-anonymous block box or a text node. ``` Then later there is an [candidate examination](https://drafts.csswg.org/css-scroll-anchoring-1/#candidate-examination) algorithm given for calculating the anchor node. This algorithm doesn't make any mention of how to handle inline elements, so it's not clear how we're supposed to guarantee that the anchor node is only a non-anonymous block box or text node. Blink will descend into them to find an anchor node, and then continue if one is not found. This is the sane thing to do, and how we've implemented it in Gecko, but it should be made more explicit in the algorithm. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3489 using your GitHub account
Received on Monday, 7 January 2019 18:48:55 UTC