- From: shans via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Oct 2016 08:08:04 +0000
- To: public-houdini-archive@w3.org
(nit: as of TPAC, unregistered properties are substituted as strings,
not lists of tokens).
It's interesting that there are two truthy-feeling principles opposed
here:
1. the computed value of a registered custom property shouldn't differ
from the computed value part of a property that references that
custom property (when the types align)
2. registering a custom property shouldn't change its behavior
(1 means roughly that you shouldn't ever be able to have
```
--foo: [something];
property-with-type-matching-foo: var(--foo);
```
and `getComputedStyle(el).getPropertyValue('--foo') !==
getComputedStyle(el).getPropertyValue('property-with-type-matching-foo');`
)
I don't really know what to do here. It does seem deeply weird for the
variable to not resolve relative to the variable sheet when you know
up-front that it is a url().
--
GitHub Notification of comment by shans
Please view or discuss this issue at
https://github.com/w3c/css-houdini-drafts/issues/321#issuecomment-251894635
using your GitHub account
Received on Thursday, 6 October 2016 08:08:19 UTC