Closed Bug 774386 Opened 12 years ago Closed 18 days ago

CrossProcessCompositorParent shouldn't assume there's only one CompositorParent

Categories

(Core :: Graphics: Layers, defect)

defect

Tracking

()

RESOLVED INVALID

People

(Reporter: cjones, Unassigned)

References

Details

In bug 745148 we assume there's only one CompositorParent.  Nico built most of the machinery we need to remove that assumption.  The problem is, given an nsIWidget/LayerManager on the main thread, it's quite hairy and somewhat expensive to find out what its compositor ID is.

When we fix that problem, we can associate CrossProcessCompositorParents with compositor IDs and remove this assumption.
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 18 days ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.