Re: [csswg-drafts] [css-sizing] Last remembered size for non-atomic inlines? (#7606)

The CSS Working Group just discussed `[css-sizing] Last remembered size for non-atomic inlines?`, and agreed to the following:

* `RESOLVED: display:inline doesn't record a size`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: [css-sizing] Last remembered size for non-atomic inlines?<br>
&lt;fantasai> github: [css-sizing] Last remembered size for non-atomic inlines?<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/7606<br>
&lt;fantasai> oriol: Spec doesn't clarify the details of what size we are recording as the last remembered size<br>
&lt;fantasai> oriol: for non-atomic inline elements, it's hard to determine a size<br>
&lt;fantasai> oriol: ? has a size of 0x0<br>
&lt;fantasai> oriol: when recording a size, we have two resonable ways<br>
&lt;fantasai> oriol: one is to store 0x0 as usual<br>
&lt;fantasai> oriol: this is what implementations are currently doing<br>
&lt;fantasai> oriol: might be a bit surprising since not the real size, just an arbitrary decision<br>
&lt;fantasai> oriol: another possibility would be doing the same that we do for display:none or when not generating a box<br>
&lt;fantasai> oriol: we are not storing the last remembered size<br>
&lt;fantasai> oriol: and we allow the element to keep a previously-set last remembered size<br>
&lt;fantasai> oriol: I don't have a strong opinion<br>
&lt;fantasai> oriol: bit of an edge case, since inline elements do not support size containment<br>
&lt;fantasai> oriol: so this will only matter if you are dynamically changing the display from 'inline' to other things<br>
&lt;fantasai> oriol: but would like to clarify expected behavior<br>
&lt;fantasai> astearns: when you say Chrome and FF are treating inlines as 0x0<br>
&lt;fantasai> astearns: WebKit result is different? or don't know?<br>
&lt;fantasai> oriol: I think WK has not implemented this feature<br>
&lt;fantasai> TabAtkins: I have no attachment to either solution<br>
&lt;fantasai> TabAtkins: in absence of a reason for a change, would stick with existing behavior<br>
&lt;fantasai> dholbert: Seems weird to have different behaviors for transiently display:none vs display:inline<br>
&lt;fantasai> dholbert: without a good reason for 0x0 it feels arbitrary to have those differ<br>
&lt;fantasai> dholbert: what happens if you 'display: contents' or other value?<br>
&lt;fantasai> dholbert: would be best to have a consistent answer to "no sensible size"<br>
&lt;fantasai> TabAtkins: that's fair<br>
&lt;fantasai> astearns: other opinions?<br>
&lt;fantasai> [silence]<br>
&lt;fantasai> astearns: Proposed resolution is to not accept current behavior in impls, but go with option 2 of not recording the size<br>
&lt;fantasai> astearns: any objections?<br>
&lt;fantasai> RESOLVED: display:inline doesn't record a size<br>
</details>


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


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

Received on Wednesday, 7 September 2022 23:26:30 UTC