#4538 closed bug (invalid)
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 (4)
Changed 14 years ago by
| Attachment: | pushstack-selector.patch added |
|---|
comment:3 follow-up: 5 Changed 12 years ago by
| Keywords: | needsreview added |
|---|---|
| Milestone: | 1.4 |
| Resolution: | → invalid |
| Status: | new → closed |
comment:4 Changed 12 years ago by
| Keywords: | needsreview removed |
|---|
comment:5 Changed 12 years ago by
Replying to 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.
Note: See
TracTickets for help on using
tickets.
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.