Solution -> Ticket #9521 http://bugs.jquery.com/ticket/9521#comment:3

Is there anyway you could reduce that overkill to something simple and straight forward that merely illustrates the issue...?

Reduced test case:

http://jsfiddle.net/rwaldron/wFJ8N/

FWIW, I think it's obscene that HTML5 puts no restrictions on the characters that can be used in attribute values

Thanks a lot! I didn't know that Firebug Lite is available. It is very simple!

FWIW, I think it's obscene that HTML5 puts no restrictions on the characters that can be used in attribute values

I think so, too about "class" attribute.

But attributes are not only "class". "value" and "data-*" attributes are expected to store any data.

And it is possible to include every attributes in a query selector.

http://jsfiddle.net/dFJwx/2/

And jQuery document says:

http://api.jquery.com/category/selectors/

If you wish to use any of the meta-characters ( such as !"#$%&'()*+,./:;<=>?@[\\]^`{|}~ ) as a literal part of a name, you must escape the character with two backslashes: \\\\.

So I think it should be fixed.

This problem is caused by existing two context, "Selector" and "DOM creation", in a same signature $(string).

I think jQuery's main work is Selector. But DOM creation interrupts it.

Fortunately, There is no selector starts with '<'.

So I agree with suggestion in #9521.

Do you think it has any problem in this suggestion?

Thank you.

First of all, I think you misunderstood me - I said nothing about "class" attributes specifically; I meant _all_ attributes. It has nothing to do with the sizzle/selectors, but everything to do with the regular expression used to determine which branch of logic should be used.

Closing as duplicate, however this is not a 1-to-1 duplicate, simply that fixing 9521 will also resolve this issue

Duplicate of #9521.