- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Nov 2018 17:38:36 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Case-sensitive attribute selectors`, and agreed to the following: * `RESOLVED: Add a Sensitive 's' flag` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Case-sensitive attribute selectors<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/2101<br> <dael> TabAtkins: Turns out there's a couple of HTML attributes that must be matched case insensitive in selectors.<br> <dael> TabAtkins: We let UAs or Authors match case insensitive for UA stylesheet. Type attribute requires this.<br> <dael> TabAtkins: ol uses type in way that requires case sensitivity<br> <dael> TabAtkins: Because type elsewhere requires case insensitive it would be weird and bad if some were sensitive and some not. Just like we added i tag to allow authors to opt in, we can do opposite to force case sensitive.<br> <dael> TabAtkins: Put in a UA style sheet and in a few places where author needs to match against case sensitive they use that.<br> <dael> fantasai: I don't have obj to adding the flag. Confused as to why type attribute it's inherently case sensitive on ol<br> <dael> dbaron: It's per attribute, not attribute+element. attribute+element is a lto more complicated and this is only use case<br> <dael> TabAtkins: I like s as the flag. Insensitive = i, Sensistive=s<br> <florian> +1 to "s"<br> <dael> fantasai: Agreed<br> <dael> astearns: Obj to adding a Sensistive 's' flag?<br> <dael> RESOLVED: Add a Sensitive 's' flag<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2101#issuecomment-438751096 using your GitHub account
Received on Wednesday, 14 November 2018 17:38:37 UTC