Bug 1493369 Comment 38 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
The root cause appears to be that when we send update events we sometimes optimize the update list so e.g. deleting something and added it again we may do this:

```js
if (action === "added") {
      // If the same store name was previously deleted or changed, but now is
      // added somehow, don't send the deleted or changed update.
      this.removeNamesFromUpdateList("deleted", storeType, data);
      this.removeNamesFromUpdateList("changed", storeType, data);
    }
```

This means we can't simply check for all update events... we need to ignore updates and wait until the list of storage objects has the correct values.
Revision 1 by
on 
The root cause appears to be that when we send update events we sometimes optimize the update list so e.g. deleting something and added it again we may do this:

```js
if (action === "added") {
  // If the same store name was previously deleted or changed, but now is
  // added somehow, don't send the deleted or changed update.
  this.removeNamesFromUpdateList("deleted", storeType, data);
  this.removeNamesFromUpdateList("changed", storeType, data);
}
```

This means we can't simply check for all update events... we need to ignore updates and wait until the list of storage objects has the correct values.

Back to Bug 1493369 Comment 38