Closed
Bug 1301623
Opened 9 years ago
Closed 7 years ago
evalInSandbox for firstPartyDomain
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
RESOLVED
DUPLICATE
of bug 1297687
People
(Reporter: allstars.chh, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [tor][domsecurity-backlog1])
Like Bug 1260917, we need to check if we need to do the same thing for firstPartyDomain.
|
Reporter | |
Updated•9 years ago
|
Whiteboard: [tor][domsecurity-backlog1]
|
||
Updated•8 years ago
|
Priority: -- → P3
|
|
Reporter | |
Updated•8 years ago
|
Summary: Sandbox for firstPartyDomain → evalInSandbox for firstPartyDomain
|
||
Comment 1•8 years ago
|
||
Yoshi, what's our plan for this bug?
Do you think this is important? If so, you or Tim should take this; otherwise we just leave it as backlog.
Flags: needinfo?(allstars.chh)
|
|
Reporter | |
Comment 2•8 years ago
|
||
I filed this for Bug 1260917, so forward the ni to Tim.
Flags: needinfo?(allstars.chh) → needinfo?(tihuang)
|
||
Comment 3•8 years ago
|
||
I think it is not so important at this moment since the javascript sandbox here is for chrome code. So, basically, the content will not use this feature. However, It could be used in addon, but the addon is going to be deprecated. Therefore, the priority of this bug shouldn't be high, and we can leave it as backlog.
Flags: needinfo?(tihuang)
|
||
Comment 4•7 years ago
|
||
At the moment, SandboxOptions dictionary supports OriginAttributes. Passing firstPartyIsolation can be done in that way.
I mark this issue as dup of bug 1297687.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•