Open
Bug 961689
Opened 10 years ago
Updated 2 years ago
Process-isolated sandboxed iframes
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Core
DOM: Core & HTML
Tracking
()
NEW
Fission Milestone | Future |
People
(Reporter: bruant.d, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
See discussion on dev.platform https://groups.google.com/forum/#!topic/mozilla.dev.platform/lwzsJtZVf7Q
Reporter | ||
Comment 1•10 years ago
|
||
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.
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to David Bruant from comment #1) > <iframe sandbox="allow-javascript"> sandbox="allow-scripts" of course
Updated•10 years ago
|
Depends on: nested-oop
Reporter | ||
Comment 3•8 years ago
|
||
Feeling that this helped moving the needle forward https://bugzilla.mozilla.org/show_bug.cgi?id=1238160
Reporter | ||
Comment 4•8 years ago
|
||
Related in some way as well : https://bugzilla.mozilla.org/show_bug.cgi?id=1207306
Updated•6 years ago
|
Blocks: oop-frames
Updated•6 years ago
|
Blocks: site-isolation
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Priority: P3 → P2
Updated•5 years ago
|
No longer blocks: fission, site-isolation
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Relevant Chromium bug to follow:
https://bugs.chromium.org/p/chromium/issues/detail?id=510122
Updated•5 years ago
|
Type: defect → enhancement
Fission Milestone: --- → Future
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•