Open
Bug 1513262
Opened 6 years ago
Updated 2 years ago
Can we remove the allowWaivers sandbox option?
Categories
(Core :: XPConnect, enhancement, P3)
Core
XPConnect
Tracking
()
NEW
People
(Reporter: jandem, Unassigned)
References
Details
This was requested and implemented in bug 1182409 but it has been three years and only test_allowWaivers.js uses it AFAICS.
|
Reporter | |
Updated•6 years ago
|
Flags: needinfo?(bobbyholley)
|
||
Comment 1•6 years ago
|
||
We really _should_ be setting this for WebExtension scripts. Is there a reason we aren't?
Flags: needinfo?(bobbyholley)
|
||
Comment 2•6 years ago
|
||
(In reply to Bobby Holley (:bholley) from comment #1)
> We really _should_ be setting this for WebExtension scripts. Is there a
> reason we aren't?
We allow extensions to use waivers to expose APIs to content pages.
|
|
||
Comment 3•6 years ago
|
||
I talked to Bill about the possibility of only allowing them for plain objects, not DOM nodes, but he left before he had a chance to work on it.
|
||
Updated•6 years ago
|
Priority: -- → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•