- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 21 Jan 2026 16:38:10 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-anchor-position-1] Clarify how anchor-scope works with display:contents`, and agreed to the following: * `RESOLVED: anchor-scope and similar scoping properties operate on the flattened element tree (not box tree)` <details><summary>The full IRC log of that discussion</summary> <ydaniv> TabAtkins: question about how anchor-scope works with display: contents<br> <ydaniv> ... we can use scope on element and scope to local tree<br> <ydaniv> ... question is what happens when on display: contents element<br> <ydaniv> ... so what exactly is the scope of anchor-scope? flat-tree?<br> <ydaniv> ... box tree?<br> <ydaniv> ... I think it should be element relationship tree<br> <emilio> Tab's suggestion in the issue wfm<br> <fantasai> +1 to using element tree<br> <ydaniv> ... otherwise some APIs may break the feature<br> <flackr> +1<br> <andruud> FYI: https://github.com/w3c/csswg-drafts/issues/10325<br> <ydaniv> ... so proposing the flat element tree, not the box tree<br> <ydaniv> andruud: based on previous discussion in github<br> <TabAtkins> previous resolution was about flat vs Dom tree<br> <ydaniv> ... I believe it's on element tree<br> <vmpstr> q+<br> <TabAtkins> this is about flat tree vs box tree<br> <astearns> ack vmpstr<br> <ydaniv> astearns: proposal is to use the element tree, not box tree<br> <ydaniv> vmpstr: we have trigger-scope that behaves the same, will this change apply to other properties?<br> <ydaniv> TabAtkins: yes, should apply to all scoping properties<br> <fantasai> PROPOSED: anchor-scope and similar scoping properties operate on the flattened element tree (not box treE)<br> <flackr> +1<br> <fantasai> RESOLVED: anchor-scope and similar scoping properties operate on the flattened element tree (not box tree)<br> <ydaniv> astearns: so resolution is that it will affect all scoping proerties<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12783#issuecomment-3779508392 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 January 2026 16:38:11 UTC