- From: Marat Tanalin <mtanalin@yandex.ru>
- Date: Thu, 01 Oct 2015 00:10:57 +0300
- To: Henrik Andersson <henke@henke37.cjb.net>, Anne van Kesteren <annevk@annevk.nl>, "www-style@w3.org" <www-style@w3.org>
- Cc: Domenic Denicola <d@domenic.me>
30.09.2015, 21:07, "Henrik Andersson" <henke@henke37.cjb.net>:
> Marat Tanalin skrev:
>> To match elements with unsupported values of an attribute, we could introduce a functional pseudoclass like `:unsupported-attr-value()` with an attribute name as argument. For example:
>>
>> INPUT:unsupported-attr-value(type) {
>> /* Styles for INPUTs that have unsupported value of `type` attribute. */
>> }
>
> Except that wont work here. There is at least one supported type that
> will lead to this behavior.
I'm not sure what you mean, but having a pseudoclass for unsupported attribute value does not make us losing ability to use multiple comma-separated selectors, e.g.:
INPUT:unsupported-attr-value(type),
INPUT:not([type]),
INPUT[type="text"] {
/* Styles for text fields. */
}
Received on Wednesday, 30 September 2015 21:11:32 UTC