Open Bug 1531498 Opened 7 years ago Updated 4 years ago

Get PeerIdentity working in a post Fission world

Categories

(Core :: WebRTC, enhancement, P3)

enhancement

Tracking

()

Fission Milestone Future

People

(Reporter: drno, Unassigned)

Details

As the IdP for PeerIdentity can be loaded from the different domain once Fission is turned on the IdP will run in a different process from the content page it needs to communicate with.

In other words: we are expecting that Fission will brake PeerIdentity and we need to fix it.

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?

Tracking for Fission Nightly (M6)

Fission Milestone: ? → M6
Summary: Get PeerIdentity working in a post fission world → Get PeerIdentity working in a post Fission world

I'm setting this to Future since as far as I know PeerIdentity is not supported by any other browsers and so getting this working should not block Fission.

Fission Milestone: M6 → Future

It a working feature, which would break once we turn on Fission. So it could be argued that it should be fixed before Fission rides the trains. But it's usage is super low, so I'm okay with Future as well.

Assignee: drno → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.