Ticket #9278 (closed bug: wontfix)
unbind is too greedy when unbinding proxy functions
|Reported by:||sahab.yazdani+jquery@…||Owned by:||rwaldron|
Steps to reproduce:
- Create two proxies of the same function but using different contexts.
- Bind these two proxies unto the same event handler using $().bind
- Unbind one of the proxies using the proxied function handle
- Trigger the event
Note that no event gets triggered
The version of the handler that was not unbound should get triggered.
The JSFiddle will clarify this: http://jsfiddle.net/RD7ZF/7/
As far as I can tell, jQuery has worked like this from the dawn of time, but to me the behviour is rather unexpected. Because the contexts for the proxy functions are different, by extension the two proxy methods are different whereas unbind treats them as being the same.
- Owner set to rwaldron
- Status changed from new to assigned
- Component changed from unfiled to event
- Status changed from assigned to closed
- Resolution set to wontfix