- From: Jonathan Chan via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Jul 2017 18:20:24 +0000
- To: public-houdini-archive@w3.org
Actually, it seems like maybe something even stronger (like the following) would be needed: > ## font-size dependency cycles > Use of `em` units in typed custom property declarations can lead to dependency cycles involving the declaration for `font-size`, the directed tree of dependencies with `font-size` at its root has a node corresponding to a registered custom property whose syntax would require computations depending on the font-size, and either uses `em` units in its declaration, or has some child in the dependency tree corresponding to a variable whose declaration includes a dimension token with an `em` unit. This is because even if the `n em` dimension token is not contained in the literal text of a declaration for a typed custom property whose syntax would require the font-size, an `n em` token might end up being substituted for a variable reference to another property which might not even require such computation; for example, an unregistered custom property, or one declared with syntax `*`. -- GitHub Notification of comment by jyc Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/315#issuecomment-317075746 using your GitHub account
Received on Friday, 21 July 2017 18:20:24 UTC