Re: [csswg-drafts] [cssom] Table row resolved width and height. (#4444)

The CSS Working Group just discussed `[cssom] Table row resolved width and height`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [cssom] Table row resolved width and height<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4444<br>
&lt;dael> emilio: Height doens't apply to table rows depending on writing modes. There was interop issue found by jquery folks. A bunch of discussion on the issue.<br>
&lt;dael> emilio: Various options. Nice to get an agreement.<br>
&lt;dael> emilio: Webkit and Chrome behavior doesn't roundtrip. I propose to return computed value which is what we do for other elements that don't support height. People argued against that<br>
&lt;dael> TabAtkins: I'll proxy Alex and say FF is correct and roundtrip should work. Let's roll<br>
&lt;dael> astearns: Reading thread. What needs to be done to roundtrip height?<br>
&lt;dael> emilio: Using the computed value works. FF does give a resolved value it just roundtrips so not what I proposed.<br>
&lt;dael> emilio: Edge used to report auto<br>
&lt;dael> emilio: And the computed value<br>
&lt;dael> emilio: Computed value of auto FF gets a roundtrip height and Blink doesn't make sense. Edge returned computed value which is consistent with inlines<br>
&lt;dael> astearns: Prop: Return the computed value of height for table rows<br>
&lt;dael> emilio: When it doesn't apply which is not always. Depends on writing mode<br>
&lt;dael> emilio: I think that makes most sense. Alex argued for FF behavior. There are other comments from fremy and oriol saying computed value may not be most useful<br>
&lt;dael> emilio: A bunch of use cases for this<br>
&lt;dael> fantasai: Seems there are two discussions. One is which property applies and therfore has meaningful value. And which is in height axis of table. Then should prop of block axis return auto or used value.<br>
&lt;dael> fantasai: Mapping question should be switching based on writing mode of table. In terms of if we return used value or auto I don't have option other than it hsould round trip<br>
&lt;dael> fantasai: Means block axis on row needs to return. Can't default to auto. Inline axis doesn't matter<br>
&lt;dael> emilio: Used to have stronger opinion but I'm happy to keep discussing and figure out best compromise. If people don't have strong opinion<br>
&lt;dael> astearns: Leave that intent is to have round trip for block axis and leave it at that until we have actual text?<br>
&lt;dael> emilio: Fair<br>
&lt;dael> astearns: Concerns with having round trip value for block axis of table rows?<br>
&lt;dael> astearns: Let's work in issue<br>
</details>


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

Received on Wednesday, 15 January 2020 17:53:27 UTC