| component: |
unfiled → selector
|
| priority: |
undecided → high
|
| resolution: |
→ duplicate
|
| status: |
new → closed
|
Thanks for taking the time to contribute to the jQuery project by writing a bug report and providing a test case!
After checking your report and your test case I determined that this is a already known bug. You can check the ticket mentioned below for progress on this issue.
In case it's not clear why the "direct" selector ($(...)) works but with filter(...) doesn't or why these two bugs have indeed the same root cause:
- The "direct" selector only works in browsers that support qSA (just try your fiddle e.g. in IE6 and notice how the 2nd and 3rd test fail).
- The bug are the same because
.filter(...) uses Sizzle also for qSA-aware browsers.
P.S.: As some other selector related bugs have been fixed for jQuery .1.5 you can work around this problem (when using 1.5) by escaping the dot in your filter selector like this .filter("[id^='Favourite[Music]\\\\.Song[Jazz]']")
Thanks for taking the time to contribute to the jQuery project by writing a bug report and providing a test case!
After checking your report and your test case I determined that this is a already known bug. You can check the ticket mentioned below for progress on this issue.
In case it's not clear why the "direct" selector (
$(...)) works but withfilter(...)doesn't or why these two bugs have indeed the same root cause:.filter(...)uses Sizzle also for qSA-aware browsers.P.S.: As some other selector related bugs have been fixed for jQuery .1.5 you can work around this problem (when using 1.5) by escaping the dot in your filter selector like this
.filter("[id^='Favourite[Music]\\\\.Song[Jazz]']")