Opened 14 years ago
Closed 13 years ago
#4539 closed bug (fixed)
live with context in jquery nightly
| Reported by: | trixi | Owned by: | brandon |
|---|---|---|---|
| Priority: | major | Milestone: | 1.4 |
| Component: | event | Version: | 1.3.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
You have added support for live with a different context than document (see here: http://dev.jquery.com/ticket/4189), but the fix is not complete yet. If a parent element of the choosen context also matches the given selector-string, the live event will also fire.
I have added two patches for this.
Attachments (3)
Change History (5)
Changed 14 years ago by
| Attachment: | event-live-context.patch added |
|---|
Changed 14 years ago by
| Attachment: | closest-live-context.patch added |
|---|
Changed 14 years ago by
| Attachment: | closest-context.patch added |
|---|
comment:1 Changed 14 years ago by
Good catch.
This has made me think that closest should be restricted to not traverse higher than the current jQuery context anyway - I attached a patch for this. And maybe the same should apply for other upward traversals too, ie. parent/parents.
Ah, I've just discovered this is not such a good idea. As jQuery doesn't accept an element as selector and context, so the following wouldn't work:
$(event.target, context).closest('.something')
Ok, ignore my patch! I'd remove it but can't find a way to in trac!
comment:2 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
It looks like this was landed as part of the recent live commits.
Restrict closest to search only within the jQuery context