Re: [csswg-drafts] [css-contain][css-anchor-position-1] Should size/layout containment also contain anchor names? (#9349)

The CSS Working Group just discussed `[css-contain][css-anchor-position-1] Should size/layout containment also contain anchor names?`, and agreed to the following:

* `RESOLVED: Layout containment contains anchor names and size containment/paint containment do not`

<details><summary>The full IRC log of that discussion</summary>
&lt;keithamus> TabAtkins: already in spec that style containment triggers containment of anchor names<br>
&lt;keithamus> TabAtkins: should other containments have this? Layout containment should for the same reason that it censors baselines. If it didn't you'd have to do layout in the subtree.<br>
&lt;keithamus> TabAtkins: defeats point of containment<br>
&lt;keithamus> TabAtkins: size containment should depend on children size and layout children etc. No guarantees are made about being able to defer work on layout containment<br>
&lt;keithamus> TabAtkins: size containment should not scope anchor names<br>
&lt;emilio> q+<br>
&lt;keithamus> TabAtkins: we use size containment as a cycle breaker a lot.<br>
&lt;miriam> q+<br>
&lt;keithamus> TabAtkins: scoping it means you wouldnt be able to use container queries and anchor names on the same page.<br>
&lt;keithamus> TabAtkins: paint containment doesn't for the same reason<br>
&lt;astearns> ack emilio<br>
&lt;keithamus> emilio: I guess scoping would work both inside and outside right?<br>
&lt;keithamus> TabAtkins: no<br>
&lt;keithamus> emilio: so some kind of named scoping? I don't see how they change the constraints?<br>
&lt;keithamus> emilio: if a name bleeds inside a layout contained thing...<br>
&lt;keithamus> emilio: does layout containment also scope counter names and so on?<br>
&lt;keithamus> TabAtkins: no and it shouldn't. You dont need to do layout for counter names, just box tree.<br>
&lt;keithamus> emilio: I was just confused about what point and where in the dependency tree<br>
&lt;astearns> ack miriam<br>
&lt;keithamus> miriam: container queries add layout containment as well. Even if we restrict on layout containment we still have problems on how these two interact.<br>
&lt;keithamus> miriam: you cant use anchoring across different containers<br>
&lt;keithamus> futhark: you can't anchor something inside the size container outside, or vice versa<br>
&lt;keithamus> TabAtkins: regardless if we allowed names to leak out of layout containment it defeats the point of layout containment.<br>
&lt;keithamus> TabAtkins: I think it's still a requirement that layout containment scopes the values<br>
&lt;keithamus> miriam: should we open a new issue to resolve how these two interact?<br>
&lt;keithamus> astearns: a developer need to use these across boundaries trumps the need for good optimisations<br>
&lt;keithamus> chrishtr: resolve this then raise new issue?<br>
&lt;keithamus> astearns: yes resolve this issue and then work out how it interacts, revisit it if it turns out there's a need to anchor across boundaries<br>
&lt;keithamus> astearns: did futhark's remarks change your position TabAtkins?<br>
&lt;keithamus> TabAtkins: same. It only matters for style queries<br>
&lt;keithamus> futhark: no it's also generated compute from... layout on outside<br>
&lt;keithamus> TabAtkins: that's not in the spec right now as far as I can tell<br>
&lt;keithamus> futhark: yes, container type size also applies layout, size, containment<br>
&lt;keithamus> futhark: this is not a problem specific to layout containment, also style containment...<br>
&lt;keithamus> TabAtkins: okay. Let's discuss that in the new issue<br>
&lt;keithamus> PROPOSED RESOLUTION: Layout containment contains anchor names<br>
&lt;keithamus> PROPOSED RESOLUTION: Layout containment contains anchor names and size containment/paint containment do not<br>
&lt;keithamus> RESOLVED: Layout containment contains anchor names and size containment/paint containment do not<br>
&lt;keithamus> TabAtkins: I have an anchor breakout session in the w3 breakout sessions to resolve the remaining issues. Provisional time slot for now.<br>
&lt;keithamus> astearns: we can use that session for a wider audience hopefully<br>
&lt;keithamus> fantasai: those breakouts are for across w3. So we want to resolve issues on our own, but discuss stuff with the broader community in the breakout<br>
&lt;keithamus> TabAtkins: I thought it was the same as TPAC wednesday.<br>
&lt;keithamus> astearns: we'll figure out some extra meeting times.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9349#issuecomment-1981484044 using your GitHub account


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

Received on Wednesday, 6 March 2024 18:01:41 UTC