Closed Bug 1317843 Opened 3 years ago Closed 3 years ago
Manager Composite into two classes
We want to have a base class that LayerTransactionParent interacts with and just adds the necessary 'parent side' functions required, and then a separate class that actually implements this on top of the Compositor API. This way we can have alternate implementations of LayerManager that don't use Compositor.
Attachment #8811068 - Flags: review?(jmuizelaar) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/880e9106f46d Split LayerManagerComposite into two classes. r=jrmuizel
You need to log in before you can comment on or make changes to this bug.