- From: Henrik Andersson <henke@henke37.cjb.net>
- Date: Wed, 30 Sep 2015 23:32:30 +0200
- To: Marat Tanalin <mtanalin@yandex.ru>, Anne van Kesteren <annevk@annevk.nl>, "www-style@w3.org" <www-style@w3.org>
- Cc: Domenic Denicola <d@domenic.me>
Marat Tanalin skrev:
> 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. */
> }
>
>
Correct, you can do that. But it is still a bit redundant, having to use
three selectors when you only wanted one.
Received on Wednesday, 30 September 2015 21:33:04 UTC