evalInSandbox for firstPartyDomain

RESOLVED DUPLICATE of bug 1297687

Status

()

Core
DOM: Security
P3
normal
RESOLVED DUPLICATE of bug 1297687
2 years ago
2 months ago

People

(Reporter: allstars, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [tor][domsecurity-backlog1])

Like Bug 1260917, we need to check if we need to do the same thing for firstPartyDomain.
(Reporter)

Updated

2 years ago
Whiteboard: [tor][domsecurity-backlog1]
Priority: -- → P3
(Reporter)

Updated

2 years ago
Summary: Sandbox for firstPartyDomain → evalInSandbox for firstPartyDomain

Comment 1

2 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)
I filed this for Bug 1260917, so forward the ni to Tim.
Flags: needinfo?(allstars.chh) → needinfo?(tihuang)
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)
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
Last Resolved: 2 months ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1297687
You need to log in before you can comment on or make changes to this bug.