Re: [csswg-drafts] Same behavior or alias for text-justify: inter-character and text-justify: distribute (#6156)

The CSS Working Group just discussed `Same behavior or alias for text-justify: inter-character and text-justify: distribute`, and agreed to the following:

* `RESOLVED: update spec to alias at compute time`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen_> Topic: Same behavior or alias for text-justify: inter-character and text-justify: distribute<br>
&lt;Rossen_> github: https://github.com/w3c/csswg-drafts/issues/6156<br>
&lt;dlibby_> florian: in CSS text, we say that text-justify: inter-character has an old name of distribute and has same behavior. should these be aliases, conceptually this makes sense and is what implemetnations do<br>
&lt;Rossen_> q?<br>
&lt;dlibby_> florian: Firefox implements as an alias where distribute serializes to inter-character<br>
&lt;dlibby_> fantasai: distribute was implemented in IE5, aliasing in Firefox demonstrates web compatibility, maybe we should go with that behavior<br>
&lt;dlibby_> florian: not 100% clear if aliased at parse time or computed value time, but it's being converted<br>
&lt;fantasai> s/IE5/IE5.5 (IIRC)/<br>
&lt;fantasai> s/aliasing/computing/<br>
&lt;dlibby_> emilio: we do it at computed value time, but wonder if we should do at parse time<br>
&lt;dlibby_> florian: compute time is easier to spec, parse time make sense<br>
&lt;dlibby_> emilio: we alias a lot of properties at parse time<br>
&lt;dlibby_> florian: for values, i'm not sure if it is well specified what it means for a parse-time aliasing<br>
&lt;dlibby_> emilio: the only difference is when querying specified style<br>
&lt;dlibby_> florian: we can spec Firefox behavior, or we can change to spec to desired behavior<br>
&lt;dlibby_> emilio: given that we have a lot of parse-time aliasing, maybe better to go in that direction<br>
&lt;dlibby_> fantasai: parse-time aliasing is not actually spec'd so we should figure out which direction to go<br>
&lt;fantasai> s/which direction to/where that would/<br>
&lt;dlibby_> emilio: [provides example of linear-gradient and -moz-linear-gradient]<br>
&lt;dlibby_> Rossen_: this is a good precedent to clean up and specify<br>
&lt;dlibby_> fantasai: suggest that existing impl computes, we should update spec to match impl. Separately we should define how aliasing works<br>
&lt;dlibby_> fantasai: at that point, if Gecko wants to change the text spec to use the alias definition, we can do that in a separate step<br>
&lt;dlibby_> emilio: sounds good to me<br>
&lt;dlibby_> florian: we should not leave the spec as-is, either spec what is happening today or what we want in the future<br>
&lt;dlibby_> florian: proposed resolution - update spec to match Gecko implementation<br>
&lt;dlibby_> RESOLVED: update spec to alias at compute time<br>
</details>


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


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

Received on Thursday, 8 April 2021 22:57:52 UTC