- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Oct 2018 15:29:57 +0000
- To: public-css-archive@w3.org
I'm not super dedicated to fighting this, but that sort of dependent normalization *is* a forward-compatibility risk; certain values can serialize differently depending on whether the browser recognizes it as a known property or not. I'd prefer if we always left it unchanged, in both of those places. (And in every other place we use a `<custom-ident>`.) (I presume the normalization is so that the browser can trivially check for it later in a map of property names?) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3155#issuecomment-425951130 using your GitHub account
Received on Monday, 1 October 2018 15:30:10 UTC