#3947 closed bug (worksforme)
Selectors with "$" symbol
Reported by: | simon.crowell | Owned by: | john |
---|---|---|---|
Priority: | major | Milestone: | 1.4 |
Component: | selector | Version: | 1.3.2 |
Keywords: | asp.net, selector, $ | Cc: | |
Blocked by: | Blocking: |
Description
I have ran into this problem where I was using the a star rating plugin (this is unrelated).
Essentially a selector in the prevAll method that includes a "$" in it does not work in 1.3 but does in 1.2.6. This is relevant to my application as its an asp.net app that relies on the id of the control which is generally coming out with "$" symbols in it.
I understand there would be a work around for this by removing "$" symbols.
Thanks
Attachments (1)
Change History (6)
Changed 14 years ago by
Attachment: | prevAll bug.zip added |
---|
comment:1 Changed 14 years ago by
http://docs.jquery.com/Selectors
Note: if you wish to use any of the meta-characters described above as a literal part of a name, you must escape the character with two backslashes (\). For example:
#foo\\:bar #foo\\[bar\\] #foo\\.bar
comment:2 Changed 14 years ago by
Thanks for your help. I'll post a comment about the fix for the rating plugin as well :)
Thanks
comment:3 Changed 14 years ago by
Btw IDs can't really contain $ signs: http://www.w3.org/TR/html4/types.html#h-6.2
Though it's a bit confusing that in 1.2 you didn't have to escape this, Sizzle seems to be stricter on this.
comment:4 Changed 14 years ago by
In the example there's a class selector in which the $ sign needs to be escaped but I tried that with an ID and the quickexpr
doesn't match an ID that contains any special characters. This hasn't been changed much since 1.2.6 so these expressions are handled by the selector engine, which souldn't be necessary. Or is that intentional?
comment:5 Changed 14 years ago by
Milestone: | 1.3 → 1.3.3 |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
Version: | 1.3 → 1.3.2 |
Contains Example, Change jQuery version to see different result