W3C home > Mailing lists > Public > www-validator-css@w3.org > February 2008

Re: [bug] warning on valid selector

From: Le Sage <gammaprod@worldonline.fr>
Date: Thu, 28 Feb 2008 21:45:45 +0100
Message-ID: <47C71D79.9030105@worldonline.fr>
To: www-validator-css@w3.org

I agree...

 > There is no reason - especially from the CSS perspective - why two 
attribute selectors should be "compatible".
Agree again...

 > It does not work on IE 7 in Quirks Mode [...]
I didn't try in Quirks mode, sorry. It works in standard compliant mode, 
though. I guess some JavaScript could fix this kind of problem for IE6 & 
IE7 in Quirks Mode (with a library like jQuery).

 > The bogus warning does not appear if the selector is  + examples [...]
thanks for having done these advanced tests

 > Perhaps people who wrote this part of the code just forgot to include 
the condition "and the attribute names are the same".
That's a smart & logical explanation.

 > Did I find a bug in the validator? -> I think you did.
So what should I do? Who should I contact?

I forgot to add why I use this (which is definitely not important): on 
my website, if a link targets to Engslish content (hreflang="en"), I put 
a UK/USA flag on the right of the link (with a background-image & a 
padding-right), if the link is opened by default in a new window/tab, if 
put a "new tab" icon, but what if there is both? Well, I put both. :) 
Leads to this:
a[target="_blank"] {
  background: url(_blank.png) no-repeat right;
  padding-right: 20px;

a[hreflang="en"] {
  background: url(en.png) no-repeat right;
  padding-right: 20px;

a[hreflang="en"][target="_blank"] { /* here is the warning */
  background: url(_blank_en.png) no-repeat right;
  padding-right: 20px;

Thanks for your fast answer, Yucca. :)

Le Sage
Received on Thursday, 28 February 2008 20:48:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:44 UTC