- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Dec 2017 15:21:28 +0000
- To: public-css-archive@w3.org
Maybe a bit offtopic, but in Gecko, we handle `type` attribute of list elements manually with a mechanism called "attribute mapping", and thus we don't do any case sensitive matching for that attribute in any case. What I want to say is that, stuff in rendering section isn't required to be presented as-is in browsers as far as browsers have conformant behavior, so rendering section in specs may always be able to use some magic which CSS itself doesn't really have, although I would agree there should be as little magic as possible. I suppose that making `type` attribute in CSS matched case-insensitive has its historical reason, and making it case-insensitive in content may be the easiest approach (rather than, say, having single character case-sensitive, but case-insensitive otherwise). -- GitHub Notification of comment by upsuper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2101#issuecomment-350755220 using your GitHub account
Received on Monday, 11 December 2017 15:21:30 UTC