We want this chiefly for
- animations unaffected by content script
- video unaffected by content script
It's easiest with current machinery to have a separate compositor process rather than thread. With a compositor process, we also get
- protection from crashy/leaky video drivers
An initial design for how this might work with content processes and a compositor process is at https://wiki.mozilla.org/Gecko:CrossProcessLayers. However, off-main-thread compositing is just as useful without content processes and without a compositor process.
Patches in bug 570294 (used for testing) have the initial goop needed to get a compositor process running, and some hacky gtk painting code.
Is this a WONTFIX? It would help a lot, anyway... For example Bug 599711 .
Fennec's covered by bug 725095.
OK, Bugzilla's really screwed up this morning.
Not blocking on tracking bugs, we'll go through dependencies.
Mass tracking-e10s flag change. Filter bugmail on "2be0fcce-e36a-4e2c-aa80-0e3d33eb5406".
Marking this as games:p3, since games generally don't have (CSS/image) animations or video on a page, but they run in a canvas. We don't have performance profiles of games (at least right now) where this would have been identified as the biggest bottleneck.