Open
Bug 1808911
Opened 2 years ago
Updated 2 years ago
securitypolicyviolation from Worklet can be delayed
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
NEW
People
(Reporter: tschuster, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-backlog2])
We had various test failures that seem to be caused by Worklets breaking the assumption that securitypolicyviolation events are triggered after a setTimeout(0). (bug 1785547 and bug 1785526)
I worked around this in bug 1785547 by increasing the timeout.
|
Reporter | |
Updated•2 years ago
|
|
||
Comment 1•2 years ago
|
||
is this a timing issue with worklet's exposing a more granular substep in timing than our CSP code?
I'm not sure I fully understand the issue here.
Severity: -- → S3
Priority: -- → P3
Whiteboard: [domsecurity-backlog2]
You need to log in
before you can comment on or make changes to this bug.
Description
•