Ticket #2532581 (accepted defect)
Reporter Lewis Diamond |
Opened: 07/20/12 Last modified: 11/4/12 Status: accepted Type: defect |
Owner  Eric Ferraiuolo |
Target Release: BACKLOG Priority: P3 (normal) |
|---|---|---|---|
| Summary: | A Model's `id` cannot be reset. | ||
| Description: | See http://jsfiddle.net/ldiamond/UkPeU/3/ Model.reset() should fire "change" once with all the changed attributes as well as firing "attrChange" for each attr. |
||
| Type: | defect | Observed in Version: | 3.5.1 |
| Component: | Model | Severity: | S3 (normal) |
| Assigned To: | Eric Ferraiuolo | Target Release: | BACKLOG |
| Location: | Library Code | Priority: | P3 (normal) |
| Tags: | attribute, attributeextras, reset | Relates To: | |
| Browsers: | N/A | ||
| URL: | |||
| Test Information: | |||
Change History
|
Posted: 07/20/12
|
|
Posted: 07/20/12
The coalesced change event is currently implemented by Model. It hasn't been moved down to Attribute yet (due to the cost of firing 2 events for each single attribute change) |
|
Posted: 07/23/12
So it does actually fire the `change` event on reset, but I think there's bug around the ability to reset `id` properly, and this bug was given the false notion that `reset()` wasn't firing the `change` event. |
|
Posted: 07/23/12
I updated the summary for to reflect what the underlying bug is. This seems like an issue with how Model implement its `id` attribute as an alias. The refactor to change this to using proper getter/setter functions will hopefully resolve this issue. |
|
Posted: 07/23/12
|
|
Posted: 09/19/12
Moving from 3.NEXT to BACKLOG. |
Moving to Attribute