diff options
| author | wolfbeast <mcwerewolf@wolfbeast.com> | 2019-05-25 16:01:39 +0200 |
|---|---|---|
| committer | wolfbeast <mcwerewolf@wolfbeast.com> | 2019-05-25 16:01:39 +0200 |
| commit | 9dfb9401a5d621367730ad7ebecf0387111f4618 (patch) | |
| tree | 6b5c26b6dded20979b2c7014a4d4643f61ef90c1 /application/palemoon | |
| parent | a24d62130932b8104f931f925288d3abc9105684 (diff) | |
| download | UXP-9dfb9401a5d621367730ad7ebecf0387111f4618.tar UXP-9dfb9401a5d621367730ad7ebecf0387111f4618.tar.gz UXP-9dfb9401a5d621367730ad7ebecf0387111f4618.tar.lz UXP-9dfb9401a5d621367730ad7ebecf0387111f4618.tar.xz UXP-9dfb9401a5d621367730ad7ebecf0387111f4618.zip | |
[IndexedDB] Call SendFailureResult if the actor has been destroyed.
Normally we wouldn't need to send any notifications if the actor was
already destroyed, but it can be a VersionChangeOp which needs to
notify its parent operation (OpenDatabaseOp) about the failure.
So SendFailureResult needs to be called even when the actor was
destroyed. Normal operations redundantly check if the actor was
destroyed in SendSuccessResult and SendFailureResult, therefore it's
ok to call it in all cases here.
Diffstat (limited to 'application/palemoon')
0 files changed, 0 insertions, 0 deletions