Opened 12 years ago
Closed 12 years ago
#10606 closed bug (wontfix)
#ID-selector inconsistent
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | low | Milestone: | None |
| Component: | selector | Version: | 1.6.4 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
In the theoretical case you have multiple elements on a page with the same ID, the following selectors give different results:
$('#id') $('div#id')
The first selector only returns the first occurence of the id, while the second will return a set of all elements with that id.
They should behave the same.
Change History (5)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
| Component: | unfiled → selector |
|---|---|
| Owner: | set to pcvandam@… |
| Priority: | undecided → low |
| Status: | new → pending |
Why would ever have >1 element with the same ID?
comment:3 Changed 12 years ago by
| Status: | pending → new |
|---|
That's not the point.
Of course it shouldn't happen, but with dynamically generated content it CAN happen. Fact is jQuery does not handle ID-selectors consistently.
comment:4 Changed 12 years ago by
| Status: | new → pending |
|---|
Actually, it is: http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#the-id-attribute
If you write unexpected code, unexpected things happen.
Of course it shouldn't happen, but with dynamically generated content it CAN happen. Fact is jQuery does not handle ID-selectors consistently.
If this is an issue, the problem is not jQuery, it is the code that is dynamically generating elements that share IDs. The obvious approach is to write tests for your code that assert no duplicate IDs are created.
comment:5 Changed 12 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | pending → closed |
Just so you get a clearer picture, the "inconsistency" isn't jQuery's fault either: http://jsfiddle.net/rwaldron/JZ8GX/
jsFiddle-example:
http://jsfiddle.net/y59Q7/