Closed Bug 1604078 Opened 5 years ago Closed 4 years ago

Do appropriate stuff when we propagate media feature changes into out-of-process iframes

Categories

(Core :: Layout, task, P3)

Product:
Core
Component:
Layout
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Project Flags:
Fission Milestone M6

People

(Reporter: hiro, Unassigned)

References

(Blocks 1 open bug)

Details

In bug 1596317 I am mainly focusing on MediaFeatureChangeReason::SystemMetricsChange (and others which don't require additional stuff), for some other changes such as ResolutionChange need to propagate additional information into the iframe processes.

Tracking for Fission Nightly (M6)

Fission Milestone: --- → M6

Hiro: I'm assuming we need to do this to enable Fission in Nightly? If so, I think we can put this in M6c.

Flags: needinfo?(hikezoe.birchill)

Emilio has been doing a bunch of refactoring media feature change propagation stuff, I am pretty sure now it works.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(hikezoe.birchill)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.