Side navigation
#4538 closed bug (invalid)
Opened April 15, 2009 10:39AM UTC
Closed November 17, 2010 03:44AM UTC
Last modified December 24, 2010 10:16AM UTC
pushStack generates wrong selector properties, if you use multiple selectors
| Reported by: | trixi | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | core | Version: | 1.3.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
If you use a multiple Selector like $('.context-1, .context-2').find('a'). The pushStack method creates the following selector-property: '.context-1, .context-2 a'. I have added a patch, wich adds support for the traversing methods: find, children, next and siblings.
Attachments (1)
Change History (3)
Changed November 17, 2010 03:44AM UTC by comment:1
| keywords: | → needsreview |
|---|---|
| milestone: | 1.4 |
| resolution: | → invalid |
| status: | new → closed |
Changed December 24, 2010 04:58AM UTC by comment:2
| keywords: | needsreview |
|---|
Changed December 24, 2010 10:16AM UTC by comment:3
Replying to [comment:3 dmethvin]:
The .selector property isn't publicly documented.
Ummm... the property is documented publicly http://api.jquery.com/selector/ but it also has a warning
>[...] if DOM traversal methods have been called on the object, the string may not be a valid jQuery selector expression.
The .selector property isn't publicly documented. It's used for .live but that is not supported in combination with filtering methods such as .find(). It is not our intention to provide a documented and always-accurate .selector property. Do not use the .selector property for any external needs. It may be changed in the future. The first rule of the .selector property is that you don't talk about the selector property.