Re: [csswg-drafts] [css-position] Behaviour of semi-replaced elements. (#6789)

The CSS Working Group just discussed `[css-position] abspos semi-replaced elements`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: [css-position] abspos semi-replaced elements<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/6789<br>
&lt;fantasai> iank_: Bunch of history here<br>
&lt;fantasai> iank_: When we have width/height=auto<br>
&lt;fantasai> iank_: can either shrink-to-fit or stretch in that axis<br>
&lt;fantasai> iank_: in Grid Layout, most items will stretch except replaced elements<br>
&lt;fantasai> iank_: every layout mode make these decisions<br>
&lt;fantasai> iank_: semi-replaced element in block layout, frex, is shrhink-to-fit<br>
&lt;fantasai> iank_: Question is about abspos semi-replaced element, say with inset: 0<br>
&lt;fantasai> iank_: Firefox stretches in block axis, shrink in inline<br>
&lt;fantasai> iank_: webkit stretch both axes<br>
&lt;fantasai> iank_: chrome ...<br>
&lt;fantasai> iank_: So what do we want to do here?<br>
&lt;fantasai> iank_: previously FF team strongly wanted shrink-to-fit here<br>
&lt;fantasai> Rossen_: anyone from FF?<br>
&lt;TabAtkins> As I said in the issue a few minutes ago, "every divergence that buttons make from a standard inline-block is unfortunate."<br>
&lt;fantasai> Rossen_: Do we shrink-to-fit in both axes, or stretch in both axes, to make behavior symmetric and consistent<br>
&lt;TabAtkins> Because it has been asserted quite confidently in the past by implementors that buttons were *not* replaced elements, and were fully described solely by inline-block behavior ^_^<br>
&lt;fantasai> dholbert: Don't have an answer atm, but will take a look<br>
&lt;Rossen_> q?<br>
&lt;drott> fantasai: tab and i figured that<br>
&lt;drott> fantasai: since webkit implements stretch on both axis<br>
&lt;drott> fantasai: that makes it web compatible<br>
&lt;drott> fantasai: [missed] you can always get the other behavior by switching alignment<br>
&lt;Rossen_> ack TabAtkins<br>
&lt;Rossen_> ack fantasai<br>
&lt;fantasai> TabAtkins: In the past, impl have said that buttons aren't replaced elements<br>
&lt;fantasai> TabAtkins: and fully described by inline/block behavior, so the more we can make that true the better<br>
&lt;fantasai> TabAtkins: having them stretch by default would make them match non-replaced<br>
&lt;fantasai> iank_: I'm fine either way, but historically FF folks have been very strong in their opinion wrt shrink-to-fit<br>
&lt;fantasai> Rossen_: OK, let's give dholbert some time to look through it<br>
&lt;fantasai> Rossen_: if we can resolve on this later on in the call, great, if not, bring back next week<br>
</details>


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


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

Received on Wednesday, 10 November 2021 17:33:08 UTC