documentcloud/backbone — Issue #949: change event not fired on unset when an attribute was previously set silently
Author: jeffwatts
Created: 2012-02-03 17:14:27+00:00
State: open

The following code fails to fire a change event on unset, but I would expect it to do so:

```JavaScript
var myModel = new Backbone.Model;
myModel.on("change", function () {
alert("Listener notified!"); // never called
});
myModel.set("myAttribute", "some value", {silent: true});
myModel.unset("myAttribute"); // <-- does not trigger "change," but it should
```

The change event is triggered as expected on `unset` in Backbone 0.5.3, but not in 0.9.0 or 0.9.1.

I am aware that Backbone 0.9 made triggering change events stricter than previous versions, but it seems like changing an attribute should **always** trigger a change event if `silent: true` is not passed to the method. The way that the attribute was previously set should not affect whether the current method call triggers a change event.