Closed
Bug 1142727
Opened 10 years ago
Closed 10 years ago
Service Workers should not intercept sandboxed iframes
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla39
| Tracking | Status | |
|---|---|---|
| firefox39 | --- | fixed |
People
(Reporter: bkelly, Assigned: ehsan.akhgari)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
7.12 KB,
patch
|
nsm
:
review+
|
Details | Diff | Splinter Review |
Currently the spec does not mention how sandboxed iframes should be treated. To be safe, lets simply not allow Service Workers to intercept these. If there is a loud request for them or spec consensus then we can relax this restriction.
Here is the spec issue I opened:
https://github.com/slightlyoff/ServiceWorker/issues/648
|
Assignee | |
Comment 1•10 years ago
|
||
What kinds of sandbox iframes do you suggest we should block?
Flags: needinfo?(bkelly)
|
Reporter | |
Comment 2•10 years ago
|
||
(In reply to :Ehsan Akhgari (not reading bugmail, needinfo? me!) from comment #1)
> What kinds of sandbox iframes do you suggest we should block?
All iframes with the attribute "sandbox" for now. If we can get clarity on the spec issue in comment 0, maybe we could allow interceptions of allow-same-origin.
Flags: needinfo?(bkelly)
|
|
Assignee | |
Updated•10 years ago
|
Assignee: nobody → ehsan
|
|
Assignee | |
Comment 3•10 years ago
|
||
This is temporary until we clarify what we want to do with these
iframes in the spec.
Attachment #8582557 -
Flags: review?(nsm.nikhil)
Attachment #8582557 -
Flags: review?(nsm.nikhil) → review+
|
|
Assignee | |
Comment 4•10 years ago
|
||
|
||
Comment 5•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox39:
--- → fixed
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
|
||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•