- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Oct 2020 22:49:11 +0000
- To: public-css-archive@w3.org
That's not necessarily a problem. CSS is *generally* case-insensitive in the ASCII range, but it's allowed to not be, if it wants. For example, anything specified as a `<custom-ident>` must retain the author-supplied casing, even if it's fully in the ASCII range. So it would be a slight departure from standard CSS style to make `M` and `m` have different meanings, but it's definitely possible, and I think probably a good idea. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5674#issuecomment-719067583 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 October 2020 22:49:13 UTC