Open Bug 961689 Opened 12 years ago Updated 1 year ago

Process-isolated sandboxed iframes

Categories

(Core :: DOM: Core & HTML, enhancement, P2)

Product:
Core
Component:
DOM: Core & HTML
Type:
enhancement

Tracking

()

Project Flags:
Fission Milestone Future

People

(Reporter: bruant.d, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

Depends on: 907892
Depends on: 879475
Depends on: 961694
As a first shot, if only <iframe sandbox="allow-javascript"> (no more flags) ran in parallel, it'd already be a win for web developers.
Depends on: 961711
No longer depends on: 961711
(In reply to David Bruant from comment #1) > <iframe sandbox="allow-javascript"> sandbox="allow-scripts" of course
Depends on: nested-oop
Feeling that this helped moving the needle forward https://bugzilla.mozilla.org/show_bug.cgi?id=1238160
Related in some way as well : https://bugzilla.mozilla.org/show_bug.cgi?id=1207306
Priority: -- → P3
Priority: P3 → P2
No longer blocks: fission, site-isolation
Blocks: fission
No longer blocks: oop-frames
Type: defect → enhancement
Fission Milestone: --- → Future
Severity: normal → S3
Duplicate of this bug: 1920991

Chromium has recently shipped this, looks like.

See Also: → https://issues.chromium.org/issues/40082497
You need to log in before you can comment on or make changes to this bug.