Bug Tracker

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#11306 closed bug (fixed)

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:


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: http://jsfiddle.net/epeleg/BvLwn/

Change History (2)

comment:1 Changed 4 years ago by jaubourg

  • Component changed from unfiled to deferred
  • Milestone changed from None to 1.7.2
  • Priority changed from undecided to blocker
  • Resolution set to fixed
  • Status changed from new to closed

Fixed in 1.7.2 beta.

Note: See TracTickets for help on using tickets.