Changes

Jump to: navigation, search

Platform/GFX/APZ

887 bytes added, 18:31, 4 November 2013
no edit summary
* fire async scroll events (GeckoContentController::SendAsyncScrollDOMEvent())
* schedule arbitrary actions to be performed on the Gecko thread (GeckoContentController::PostDelayedTask())
 
== Threads and processes ==
 
When OMTC is enabled on a platform (which is a requirement for using the APZC), the compositor runs on its own thread, called the '''compositor thread'''. APZCs and the APZCTreeManager can be thought of as living on the compositor thread, although they can be used in certain ways by other threads (usually the Gecko thread, or the platform UI thread if there is one). [https://mxr.mozilla.org/mozilla-central/source/gfx/layers/composite/APZCTreeManager.h APZCTreeManager.h] documents which APZCTreeManager methods can be called on which threads.
 
On B2G, there are not only multiple threads but also multiple processes, as each app (or in the case of the browser, each tab) has its own process. In this setup, only the parent process has a compositor thread, and all APZCs live in the parent process, even ones corresponding to layers from a child thread.
== Main APZ projects on the horizon ==
Confirm
85
edits

Navigation menu