- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Sep 2018 18:37:32 +0000
- To: public-css-archive@w3.org
> Should will-change explicitly mention a case-insensitive match between the custom-ident and propery name? Yes, it should. > I think the future-proofing intentions of <custom-ident> mean we shouldn't drop the property altogether like Chrome does. I don't have a strong opinion on the case in the serialization, but there's a very slightly lower risk of compat problems when introducing new properties if we preserve the case and don't drop values that aren't names of properties. Agreed; we should keep the casing for future-proofing reasons (and just general alignment with the treatment of `<custom-ident>` elsewhere). > Values that are not a case-insensitive match for a property name are rejected, i.e. specified value serializes as empty string and computed value is "auto". This violates the spec and is a bug in Chrome. The only restriction we place on the `<custom-ident>` is that it can't be a handful of keywords; other than that it accepts all `<custom-ident>` values. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3155#issuecomment-425528426 using your GitHub account
Received on Friday, 28 September 2018 18:37:34 UTC