Closed Bug 1273017 Opened 4 years ago Closed 4 years ago

Move CompositorThreadHolder into its own file

Categories

(Core :: Graphics: Layers, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla49
Tracking Status
firefox49 --- fixed

People

(Reporter: dvander, Assigned: dvander)

References

Details

Attachments

(3 files)

A bunch of files include CompositorBridgeParent just to access the compositor message loop. To make it less tempting to use this class for random stuff, I'd like to split CompositorThreadHolder into its own file and move the message loop access there.
Move CompositorThreadHolder into a separate file, and fix up callers to GetCompositorThreadHolder.

This (and the following patches) should all preserve existing behavior.
Attachment #8752633 - Flags: review?(matt.woodrow)
Attachment #8752633 - Flags: review?(matt.woodrow) → review+
Attachment #8752634 - Flags: review?(matt.woodrow) → review+
Attachment #8752635 - Flags: review?(matt.woodrow) → review+
Depends on: 1273949
You need to log in before you can comment on or make changes to this bug.