Closed Bug 1285677 Opened 8 years ago Closed 3 years ago

Figure out how to separate Flash LSOs by Container type

Categories

(Core :: DOM: Security, defect, P3)

Product:
Core
Component:
DOM: Security
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
firefox57 --- fix-optional

People

(Reporter: tanvi, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [userContextId][domsecurity-backlog3][OA])

See Bug 1280626 for some related conversation. This is a lower priority (P3) for Containers since Firefox profiles use the same Flash LSOs. Since Containers share more than profiles, the problem is likely worse for profiles than it is for Containers. We should find solutions for both Containers and Profiles if possible. Project Mortar may help solve this problem.
The suggestion of new plugin instance per container plus possibly invoking the plugin in private browsing context could - in the case of Flash - solve this problem. Its LSOs would be non-persistent, so some loss of functionality for Flash users there, but privacy and compatibility would otherwise be satisfied. I say this not knowing if the above is possible or difficult, just that it theoretically sounds like a good workaround.
Also: comment 1 pertains to containers. It does not solve the profile issue.
Whiteboard: [userContextId][domsecurity-backlog] → [userContextId][domsecurity-backlog][OA]
Whiteboard: [userContextId][domsecurity-backlog][OA] → [userContextId][domsecurity-backlog3][OA]

Flash is no longer supported

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.