W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2010

[whatwg] [html5] r4949 - [giow] (0) The CSS rules need to do attribute value matching consistently across [...]

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 30 Aug 2010 14:40:19 +0200
Message-ID: <op.vh835hhd64w2qv@anne-van-kesterens-macbook-pro.local>
On Mon, 30 Aug 2010 14:35:03 +0200, L. David Baron <dbaron at dbaron.org>  
> But the problem with adding a new general selectors feature is that
> authors will discover it and try to use it for things that aren't ok
> being ASCII-only.

Yeah, maybe. But we could define it as some kind of token feature. As far  
as I know we do not have any markup languages which use compatibility  
caseless tokens. And hopefully we are not going to introduce any either.

Alternatively you could have something like input:type(password) I  
suppose. Would work slightly better for unknown controls that fallback to  
text, too.

Or even more alternatively we could decide not to care about this being  
difficult to select since in practice people will use lowercase values.

Anne van Kesteren
Received on Monday, 30 August 2010 05:40:19 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:26 UTC