As of the current version of jQuery (1.6.0) the "has attribute" selector:
Turns out this is not a new bug. Its actually been around since at least version 1.4.4 when the bug report that mine was dup'd to was filed: Bug 7770
I use this selector extensively to test for things like the existence of custom attributes, which identify certain behavior, or to identify elements matching a state of some kind.
I am not sure why it's taken so long for this fairly simple bug to be fixed, but until it is (and perhaps even after it is, unless you can be sure your code will never be used with older versions of jQuery) use the following workaround:
The bug happens when Sizzle, jQuery's selection engine, is used to perform this selection, versus
document.querySelectorAll, a native function that older browsers do not support. Well, let's be a little more specific. A native function that Internet Explorer 6.0 and 7.0, and Firefox 3.0 do not support. Unfortunately, those web browsers continue to be in widespread use. IE6 and 7 combined make up more than 10% of the global browser share. (Firefox 3.0 is under 1% now). In some areas these are much higher, e.g. like China, where, unfortunately, one of the target audiences of a web site I maintain resides.
Sizzle doesn't match an empty-string attribute value when using the "has attribute" selector. Using the "attribute value equals" selector gets around this. I'd use both selectors, though, because there are other inconsistencies in jQuery when testing value-less attributes. Furthermore, this behavior was changed in the current 1.6.0 release, and even further, it's going to be changed back in the next release, said one of the developers in a conversation about this over my bug report. See the jQuery blog for the 1.6.0 release for some discussion about this issue.
The upshot is that I don't think one should depend on the
[attributename=""] to consistently select a valueless attribute, either, and if you need to test just for the existence of an attribute that could have a value or just be a flag, you'll definitely need to use both to account for either case.