Side navigation
#11306 closed bug (fixed)
Opened February 08, 2012 11:49AM UTC
Closed February 08, 2012 12:58PM UTC
Last modified February 08, 2012 12:59PM UTC
calling .disable() or .lock() on a $.Callbacks object breaks its fired() status
| Reported by: | epeleg | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.7.2 |
| Component: | deferred | Version: | 1.7.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
When .fire() has been called on a Callback object,
I expect .fired() on this object to return true forever.
however it seems that if I call .disable() or .lock() on the Callback object then .fired starts returning false.
you can see an example here:
http://jsfiddle.net/epeleg/thkby/
and
here:
Attachments (0)
Change History (2)
Changed February 08, 2012 12:58PM UTC by comment:1
| component: | unfiled → deferred |
|---|---|
| milestone: | None → 1.7.2 |
| priority: | undecided → blocker |
| resolution: | → fixed |
| status: | new → closed |
Changed February 08, 2012 12:59PM UTC by comment:2
Proof: http://jsfiddle.net/pZRdu/
Fixed in 1.7.2 beta.