You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not necessarily a spec issue, I just need a clarification: do fallbacks (as specified by the var() reference) for registered properties ever trigger? E.g. can foo ever been substituted here?
In Blink, I've implemented the latter such that the fallback (100px) is triggered, but now I wonder if it's more consistent that var(--reg-length, 100px) is substituted with the initial/inherited value of --reg-length. I.e. the computed value of font-size becomes the initial/inherited value of --reg-length, and the computed value of --reg-length becomes 10 x initial/inherited.
The text was updated successfully, but these errors were encountered:
Yes, registered properties can be invalid (and thus trigger fallback in var()). Properties registered with a "*" grammar and no initialValue is invalid by default, and any custom property becomes invalid if it's involved in a cyclic reference.
Not necessarily a spec issue, I just need a clarification: do fallbacks (as specified by the
var()
reference) for registered properties ever trigger? E.g. canfoo
ever been substituted here?And what about:
In Blink, I've implemented the latter such that the fallback (
100px
) is triggered, but now I wonder if it's more consistent thatvar(--reg-length, 100px)
is substituted with the initial/inherited value of--reg-length
. I.e. the computed value offont-size
becomes the initial/inherited value of--reg-length
, and the computed value of--reg-length
becomes 10 x initial/inherited.The text was updated successfully, but these errors were encountered: