- From: Henrik Andersson <henke@henke37.cjb.net>
- Date: Wed, 30 Sep 2015 20:06:57 +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, 17:09, "Anne van Kesteren" <annevk@annevk.nl>:
>> For the user agent stylesheet, there's no good way to address <input
>> type=text>, since there's many values that make the <input> element
>> end up in the Text state.
>>
>> The only way seems to be something along the lines of
>>
>> input:not([type=hidden i]):not([type=search i]):not([type=tel i])...
> 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.
Received on Wednesday, 30 September 2015 18:07:33 UTC