summaryrefslogtreecommitdiffstats
path: root/dom/security/nsContentSecurityManager.cpp
diff options
context:
space:
mode:
authorwolfbeast <mcwerewolf@wolfbeast.com>2019-05-25 16:01:39 +0200
committerwolfbeast <mcwerewolf@wolfbeast.com>2019-05-25 16:01:39 +0200
commit9dfb9401a5d621367730ad7ebecf0387111f4618 (patch)
tree6b5c26b6dded20979b2c7014a4d4643f61ef90c1 /dom/security/nsContentSecurityManager.cpp
parenta24d62130932b8104f931f925288d3abc9105684 (diff)
downloadUXP-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 'dom/security/nsContentSecurityManager.cpp')
0 files changed, 0 insertions, 0 deletions