Re: [css-houdini-drafts] [css-properties-values-api] var() references to <length> type properties with font-relative lengths

The Working Group just discussed `var() references to type properties with font-relative lengths`, and agreed to the following resolutions:

* `RESOLVED:  specify full set of unit and depdancyies and using that in exisitng variable dependancy logic. This issue is solved from there.`

<details><summary>The full IRC log of that discussion</summary>
&lt;nainar> Topic: var() references to type properties with font-relative lengths<br>
&lt;nainar> GitHub: https://github.com/w3c/css-houdini-drafts/issues/315<br>
&lt;nainar> TabAtkins: Issue has the case &lt;look at it><br>
&lt;nainar> TabAtkins: &lt;Explains issue as written in github issue><br>
&lt;nainar> TabAtkins: Preferr to lena on dependancy resolution. They should gain a dependacy on the font zie property and a cyclic dependacy would make the property invalid at computed time.<br>
&lt;nainar> dbaron: This isnt ehe only case of unit type dependacy on property.<br>
&lt;nainar> TabAtkins: Generalize to other properties too.<br>
&lt;nainar> dbaron: Is this only for typed custom props?<br>
&lt;nainar> TabAtkins: Yes.<br>
&lt;nainar> Discussion about naming typed/registered custom propries<br>
&lt;nainar> TabAtkins: Are we doing to get in this case 100px and 1000 px for font size and variable<br>
&lt;nainar> TabAtkins: Or will we get somethign invalid with font size returning to 1 em?<br>
&lt;nainar> dbaron: var reference is referencing a computed value it should be invalid.<br>
&lt;nainar> TabAtkins: Make sure I capture all teh cases that dcan cause this and add to graph. I am down with this.<br>
&lt;nainar> Rossen: &lt;agrees><br>
&lt;nainar> astearns: Property is invalid right?<br>
&lt;nainar> TabAtkins: If invalidation happens font would be invalid and retun to inherit.<br>
&lt;nainar> astearns: Typed property would be fine?<br>
&lt;nainar> TabAtkins: Yes<br>
&lt;nainar> dbaron: What about units that depend on font selection?<br>
&lt;nainar> dbaron: What if you use a calc expression in one of those units?<br>
&lt;nainar> TabAtkins: you can do this for font weight for e.g<br>
&lt;nainar> TabAtkins: they are depdant on font peropeties and if you depend on that you have a cyclic dependacy<br>
&lt;nainar> dbaron: Hard - that there is a dependacy graph in everyone's head - need to write this down<br>
&lt;dbaron> https://wiki.csswg.org/spec/property-dependencies<br>
&lt;nainar> fremy: Can you define font size as a custom property and get in the same situation?><br>
&lt;nainar> TabAtkins: NO in that case you get a percent if y9ou ask for a computedvalue<br>
&lt;nainar> fremy: so a % can stay as a % on computedtime<br>
&lt;nainar> &lt;discussion about link><br>
&lt;nainar> TabAtkins: These tables need to be translated to spec txt for completion<br>
&lt;nainar> xidorn: color and currentColor comment in issue doesnt apply. currentColor should be computed at computedvalue tinme not used value time.<br>
&lt;nainar> TabAtkins: Yes it does.<br>
&lt;nainar> tantek: People want to specify full set of unit and depdancyies and using that in exisitng variable dependancy logic<br>
&lt;tantek> s/tantek/???<br>
&lt;nainar> Rossen: Solution to this issue would fall out of it?<br>
&lt;nainar> TabAtkins: ues<br>
&lt;TabAtkins> s/ues/yes/<br>
&lt;tantek> s/???/TabAtkins<br>
&lt;nainar> RESOLVED:  specify full set of unit and depdancyies and using that in exisitng variable dependancy logic. This issue is solved from there.<br>
</details>


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

Received on Thursday, 9 November 2017 18:53:48 UTC