Closed
Bug 1273017
Opened 9 years ago
Closed 9 years ago
Move CompositorThreadHolder into its own file
Categories
(Core :: Graphics: Layers, defect)
Core
Graphics: Layers
Tracking
()
RESOLVED
FIXED
mozilla49
| Tracking | Status | |
|---|---|---|
| firefox49 | --- | fixed |
People
(Reporter: dvander, Assigned: dvander)
References
Details
Attachments
(3 files)
|
(deleted),
patch
|
mattwoodrow
:
review+
|
Details | Diff | Splinter Review |
|
(deleted),
patch
|
mattwoodrow
:
review+
|
Details | Diff | Splinter Review |
|
(deleted),
patch
|
mattwoodrow
:
review+
|
Details | Diff | Splinter Review |
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.
|
Assignee | |
Comment 1•9 years ago
|
||
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)
|
|
Assignee | |
Comment 2•9 years ago
|
||
Attachment #8752634 -
Flags: review?(matt.woodrow)
|
|
Assignee | |
Comment 3•9 years ago
|
||
Attachment #8752635 -
Flags: review?(matt.woodrow)
|
||
Updated•9 years ago
|
Attachment #8752633 -
Flags: review?(matt.woodrow) → review+
|
|
||
Updated•9 years ago
|
Attachment #8752634 -
Flags: review?(matt.woodrow) → review+
|
|
||
Updated•9 years ago
|
Attachment #8752635 -
Flags: review?(matt.woodrow) → review+
|
||
Comment 5•9 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/f18799f8f8c6
https://hg.mozilla.org/mozilla-central/rev/79da877c9d70
https://hg.mozilla.org/mozilla-central/rev/d869cb9a9e09
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox49:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
You need to log in
before you can comment on or make changes to this bug.
Description
•