Re: [csswg-drafts] [css-logical] Should the mapping for logical values depend on the element or containing block?

The Working Group just discussed `Should the mapping for logical values depend on the element or containing block?`, and agreed to the following:

* `RESOLVED: Accept proposal`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> topic: Should the mapping for logical values depend on the element or containing block?<br>
&lt;dael> github:<br>
&lt;dael> fantasai: Question was about should hte mapping for logical values depend on element or containing block. Not about logical properties, but values like float inline start or text-inline-start<br>
&lt;dael> fantasai: First thing is currently the was stated values compute to themselves. That's first question. Second is do you map against containing block or element.<br>
&lt;dael> fantasai: Supposed to depend on kind of element. test-align:start needs  to map against element. For alignment we use containing block so makes sense to do same for float b/c you don't want element to move based on content, but rahter context<br>
&lt;dael> fantasai: Proposed is no change to spec but clarify the values map to themselves<br>
&lt;dael> fantasai: I copied that in. Does anyone else have comment?<br>
&lt;dael> Rossen: Question. There are...all properties in box model, are they defined to resolve against own writing mode?<br>
&lt;dael> fantasai: Yes own. It was sometimes correct and because you have to do computation of writing mode with cascade it's much easier computation.<br>
&lt;dael> fantasai: It's unfortunate that's t he case because there's a lot of cases to use containing block writing mode for something like margins but we did element's own writing mode for simplicity.<br>
&lt;dael> fantasai: Don't have same problem for values as they resolve at layout time<br>
&lt;dael> fantasai: We should have down issue 3 first as it talks about computed<br>
&lt;dael> [logical properties issue 3, not agenda issue 3]<br>
&lt;dael> Rossen: Other opinions?<br>
&lt;fantasai> #2821<br>
&lt;dael> Rossen: I asked about box model props because they are used for aligning box and sometimes used to align content inside. Align self and content align properties and values are very similar in layout impact so one doing self and the other containing block is weird.<br>
&lt;dael> fantasai: align self:start you use containing block, align-self:self-start you use your own writing mode<br>
&lt;dael> fantasai: text-align:start your children is what's being aligned.<br>
&lt;dael> Rossen: Get it. Not making case against it. In same virtue you can say position left and right can be used to align self and padding start and end can align content box. Fromm that PoV they are similar.<br>
&lt;dael> Rossen: For box model all properites and values compute to writing mode of element itself<br>
&lt;dael> Rossen: There is discontinuity here<br>
&lt;dael> Rossen: Can live with it.<br>
&lt;dael> Rossen: Other opinions or resolve on proposal to have values that effect alignment compute in containing block. Value effect alignment of content of a box o f an element are computed in writing mode  of element itself<br>
&lt;dael> fantasai: That's what's spec in grid, flexbox, and alignment<br>
&lt;bradk> +1<br>
&lt;dael> RESOLVED: Accept proposal<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 22 August 2018 16:16:20 UTC