- From: Simon Sapin via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Oct 2016 15:50:25 +0000
- To: public-css-archive@w3.org
SimonSapin has just created a new issue for
https://github.com/w3c/csswg-drafts:
== [cssom] "case-sensitive match for a supported CSS property"? ==
In each of:
* https://drafts.csswg.org/cssom/#dom-cssstyledeclaration-setproperty
*
https://drafts.csswg.org/cssom/#dom-cssstyledeclaration-setpropertyvalue
*
https://drafts.csswg.org/cssom/#dom-cssstyledeclaration-setpropertypriority
… one of the steps is:
> If property is not a case-sensitive match for a supported CSS
property, terminate this algorithm.
… with a link to:
https://drafts.csswg.org/cssom/#supported-css-property
> The term supported CSS property refers to a CSS property that the
user agent implements, including any vendor-prefixed properties, but
**excluding custom properties**.
(Emphasis added.)
This does not match the behavior of at least Firefox and Chromium,
where the matching is (probably ASCII) case-insensitive, and custom
properties are not excluded:
```js
document.documentElement.style.setProperty("Color", "green")
document.documentElement.style.setProperty("--a", "b")
assert_equals(document.documentElement.style.getPropertyValue("color"),
"green");
assert_equals(document.documentElement.style.getPropertyValue("--a"),
"b");
```
Please view or discuss this issue at
https://github.com/w3c/csswg-drafts/issues/580 using your GitHub
account
Received on Friday, 7 October 2016 15:50:36 UTC