- From: Sam Sneddon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Mar 2022 23:18:21 +0000
- To: public-css-archive@w3.org
gsnedders has just created a new issue for https://github.com/w3c/csswg-drafts:
== Clarity on whether supported legacy name aliases are supported properties ==
1. should `CSS.supports("word-wrap", "break-word")` return true or false?
2. should `CSS.supports("(word-wrap: break-word)")` return true or false?
3. should `"word-wrap" in window.getComputedStyle(document.documentElement)` be true or false?
4. should `[...window.getComputedStyle(document.documentElement)].includes("word-wrap")` be true or false?
IMO:
1. all UAs say true, which falls out from ["for string arguments"](https://drafts.csswg.org/css-cascade-5/#legacy-name-alias)
2. all UAs say true, which falls out from converting it "at parse time" (but we may want to be more explicit that we mean _any_ property name parsing, because "at parse time" is kinda unclear as to _what_ parse time)
3. all UAs say true; but this I'm unsure about what the current specs imply: does "applies in the CSSOM \[for\] property accessors"](https://drafts.csswg.org/css-cascade-5/#legacy-name-alias) effect the [generation of WebIDL attributes](https://drafts.csswg.org/cssom/#dom-cssstyledeclaration-camel-cased-attribute)?
4. all UAs supporting `word-wrap` as a legacy name alias say false; does this just fall out from the getter giving "longhand properties that are [supported CSS properties](https://drafts.csswg.org/cssom/#supported-css-property)", on the basis that they aren't supported properties (they're instead legacy name aliases)?
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7166 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 March 2022 23:18:23 UTC