#14142 closed bug (fixed)
Wrong number of elements returned in XML document with numeric IDs in Safari
| Reported by: | Owned by: | gibson042 | |
|---|---|---|---|
| Priority: | low | Milestone: | 1.11/2.1 |
| Component: | selector | Version: | 1.10.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
In a very special case find returns the wrong number of elements when used on an XML document with elements that have numeric ids. The exact conditions for this bug to occur are:
- Safari only
- The selector used is of the form "parent children"
- One of the children has an id attribute with the value corresponding to the number of children
For a detailed example see: http://jsfiddle.net/fHs96/10/
The same bug probably also occurs on HTML documents (HTML5 allows numeric ids).
Change History (8)
comment:1 Changed 10 years ago by
| Owner: | set to gibson042 |
|---|---|
| Status: | new → assigned |
comment:4 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Update Sizzle to 1.10.5. Fixes #14142.
Changeset: 0600a29256be76bd87adb547545bf7219fafb6ee
comment:6 Changed 10 years ago by
| Milestone: | None → 1.11/2.1 |
|---|
comment:7 Changed 10 years ago by
| Component: | unfiled → selector |
|---|---|
| Priority: | undecided → low |
Note: See
TracTickets for help on using
tickets.
You've certainly hit an interesting corner case... we use an unusual iteration pattern because
<NodeList>.lengthis unreliable on Internet Explorer (allowing elements with id "length" to mask the numeric property), but this shows that<NodeList>[<index>]is similarly unreliable on Safari.