Side navigation
#14141 closed bug (duplicate)
Opened July 16, 2013 07:27PM UTC
Closed August 26, 2013 04:50PM UTC
Duplicate objects returned in Safari when using find on attribute (xml)
| Reported by: | chris@baselinesystems.com | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | selector | Version: | 1.10.2 |
| Keywords: | Cc: | timmywil, gibson042 | |
| Blocked by: | Blocking: |
Description
Safari in Windows, iPhone, and iPad returns duplicate objects when using the jQuery find on attribute. All other browsers we tried return correctly.
Safari seems to only return duplicates when the returned xml data is in the hundreds of objects.
Please see example code:
In the example there should be only 155 zones in the returned data. Safari will return 162 zones with zones 183 through 189 duplicated.
Attachments (0)
Change History (3)
Changed August 20, 2013 06:29PM UTC by comment:1
| cc: | → timmywil, gibson042 |
|---|---|
| component: | unfiled → selector |
Changed August 20, 2013 08:54PM UTC by comment:2
Seems to me if this is a Safari bug and it only occurs when there are hundreds of elements, it would be better to document a workaround (of passing the results through $.unique) rather than forcing all other selections to take a hit.
However, if we could reproduce the bug easily and write a feature test and if it only affects XML, we could still keep the number of cases that need to pass through $.unique to a minimum.
This concerns me because although jQuery can "solve" the problem by passing supposedly unique sets through
$.uniqueit would have a major performance impact. That's assuming it's a Safari bug and not Sizzle, which I suppose we still need to prove by reproducing with native methods. @gibson042 or @timmywil what are your thoughts?