Re: [csswg-drafts] [css-position-3] Absolute positioning - Is the new inset & auto-size behaviour web-compatible? (#11195)

The CSS Working Group just discussed `[css-position-3] Absolute positioning - Is the new inset & auto-size behaviour web-compatible?`, and agreed to the following:

* `RESOLVED: Adopt spec text as quoted, i.e. no change to spec.`

<details><summary>The full IRC log of that discussion</summary>
&lt;ydaniv> emilio: still one issue in spec - margin auto preventing stretching<br>
&lt;ydaniv> ... need oriol to take this properly<br>
&lt;ydaniv> astearns: can we resolve on omitting this clause?<br>
&lt;ydaniv> emilio: to change the text to refer to inset properties<br>
&lt;astearns> ack fantasai<br>
&lt;ydaniv> fantasai: issue with web compat, more general<br>
&lt;ydaniv> ... applying alignment where insets were auto<br>
&lt;ydaniv> ... I think it would be ideal if we apply &lt;missed> to flexbox and grid<br>
&lt;ydaniv> ... auto affecting stretch is not impacted by web compat<br>
&lt;fantasai> https://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cdiv%20style%3D%22border%3A%20solid%3B%20display%3A%20flex%3B%20height%3A%20100px%22%3E%0A%20%20%3Cdiv%20style%3D%22background%3A%20orange%3B%20align-self%3A%20stretch%3B%20margin-top%3A%20auto%22%3Ex%3C%2Fdiv%3E%0A%3C%2Fdiv%3E<br>
&lt;ydaniv> fantasai: in flexbox margin win over streching<br>
&lt;ydaniv> ... AFAICT<br>
&lt;ydaniv> astearns: only in flexbox?<br>
&lt;fantasai> https://www.w3.org/TR/css-flexbox-1/#valdef-align-items-stretch<br>
&lt;ydaniv> fantasai: I believe grid is the same<br>
&lt;ydaniv> ... so when alignment is normal we should do ...<br>
&lt;ydaniv> ... but for strech should be compatible with what we do<br>
&lt;ydaniv> ... the alignment property didn't have any effect until recently<br>
&lt;ydaniv> ... normal should be resolve margins to 0<br>
&lt;ydaniv> ... auto margins don't win over the strechy behavior<br>
&lt;ydaniv> ... so for stretch alignment the auto margins should win<br>
&lt;ydaniv> ... just set to 0<br>
&lt;ydaniv> astearns: you're suggesing we need a change for normal?<br>
&lt;ydaniv> fantasai: no, the auto value already is correct<br>
&lt;ydaniv> astearns: maybe we need to take this back to issue?<br>
&lt;ydaniv> fantasai: oriol is describing what browsers do currently<br>
&lt;ydaniv> ... the questions is what the specs should specify<br>
&lt;fantasai> Current spec says that if alignment is normal and margins are auto, we stretch<br>
&lt;fantasai> If alignment is 'stretch' and margins are auto, we don't stretch<br>
&lt;bradk> +1 to usefulness of auto margin winning for stretch, like flex and grid.<br>
&lt;ydaniv> fantasai: if author says stretch they want it more, but compat with CSS 2 we can't change it, but can make it more like flexbox and grid<br>
&lt;fantasai> s/change it/change normal alignment/<br>
&lt;ydaniv> iank_: so this might be orthogonal<br>
&lt;fantasai> s/can make it/can make stretch alignment/<br>
&lt;ydaniv> ... changing anything for the double auto set case is not web compat<br>
&lt;ydaniv> fantasai: last comment was that this was fixed in spec<br>
&lt;ydaniv> astearns: anyone wants to argue that stretchy things would be different?<br>
&lt;ydaniv> iank_: could we add examples of who is doing what and what is intended behavior?<br>
&lt;ydaniv> fantasai: we have non-replace element, with insets set on both sides, has auto margins, has either no alignment or normal<br>
&lt;ydaniv> ... what wins? stretch? or margins?<br>
&lt;ydaniv> ... on normal behavior strech behavior wins<br>
&lt;ydaniv> ... that needs to be how we define normal<br>
&lt;iank_> https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=13699<br>
&lt;iank_> this case?<br>
&lt;ydaniv> ... what I'm arguing is for stretch alignment when we have room to make adjustments we<br>
&lt;fantasai> ... for stretch, s/when/where/<br>
&lt;ydaniv> ... be compat with flexbox and grid<br>
&lt;ydaniv> iank_: seems fine<br>
&lt;ydaniv> fantasai: proposal is to adopt spec as quoted and not as suggested<br>
&lt;ydaniv> astearns: suggest to close and open only if spec text on stretch turns wrong<br>
&lt;fantasai> PROPOSED: Adopt spec text as quoted, i.e. no change to spec.<br>
&lt;emilio> sgtm<br>
&lt;fantasai> RESOLVED: Adopt spec text as quoted, i.e. no change to spec.<br>
</details>


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


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

Received on Wednesday, 23 April 2025 16:32:15 UTC