Re: [csswg-drafts] [css-logical-1] flow-relative values should say what their computed values are

The Working Group just discussed `flow-relative values should say what their computed values are`, and agreed to the following:

* `RESOLVED: the flow relative keyword values compute to themselves, not to physical equivalents`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: flow-relative values should say what their computed values are<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2821<br>
&lt;dael> fantasai: This is that the values we spoke about compute  to self, not left or right.<br>
&lt;dael> fantasai: This is necessary for text-align property so for consistancy we should do that for all p roperties and if we don't do that CSSOM physical coord won't align<br>
&lt;dael> dbaron: Flip side is that it means anybody looking at computed values to act on them has to do something more complicated. If a web page looks at computed value they need to consider 2x possibilities. They might not and therefore have bugs<br>
&lt;dael> fantasai: Yeah but you have to do for inherited prop s why treat non-inherited differently?<br>
&lt;dael> fantasai: You have to do that on inherited.<br>
&lt;dael> dbaron: Not as strong a case for not inherited ones<br>
&lt;dael> dbaron: [missed] or maybe not<br>
&lt;dbaron> s/[missed]/and I think there are more of them,/<br>
&lt;dael> fantasai: Consistancy and so author can work in logical coord if they want to. Make these computed v alues be what they are and if browser needs to worry it should add convenience to its code before reporting to the user<br>
&lt;dael> dbaron: In the CSSOM<br>
&lt;dbaron> s/In/what about/<br>
&lt;dael> Rossen: I think giving them all the values and having them make the choice what  ot use would  be better then the result of calc that will mask what value ended up computed and trying to piece that  back to the value's origin. Esp. for inherited.<br>
&lt;dael> Rossen: I agree with dbaron it will require a bit more handling on user side but prob not that much<br>
&lt;dael> Rossen: We can always simplify later<br>
&lt;dael> dbaron: okay<br>
&lt;dael> Rossen: Other opinons or try to resolve?<br>
&lt;dael> fantasai: Also nec. if keeping previous resolution<br>
&lt;dael> Rossen: Yes, but we could revert.<br>
&lt;dael> Rossen: Objections to CSSOM exposes both logical and physical values and the resulting values are that of the cascade?<br>
&lt;dael> Rossen: Is that the summary?<br>
&lt;dael> fantasai: What..no.  Resolution is that the flow relative keyword values compute to themselves, not to physical equivellents<br>
&lt;dael> Rossen: Objections to this?<br>
&lt;dael> RESOLVED: the flow relative keyword values compute to themselves, not to physical equivalents<br>
</details>


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

Received on Wednesday, 22 August 2018 16:23:07 UTC