David Parks 4dc38ba6aa Bug 1577336: Part 7 - Move DXGI async plugin operations to compositor process r=jmathies,mattwoodrow,sotaro,mccr8 ... Previously, we created TextureD3D11 objects in the content process to back surfaces created for the plugin process. Those objects were then composited by the async ImageBridge. In order to remove Win32 kernel operations from content (including DX/GDI operations), this patch bounces the requests from content to the compositor process. The compositor process maintains 2 textures to be used for all plugin composition -- one for the plugin process and one for display. The plugin process can freely write to its texture and request composition when it is done, which triggers a blit to the display texture. This mirrors pre-existing behavior. Differential Revision: https://phabricator.services.mozilla.com/D46086 --HG-- extra : moz-landing-system : lando		2019-11-20 21:49:35 +00:00
..
base	Bug 1596090 - avoid sending plugin content to every content process whenever a content process is created, r=handyman	2019-11-16 00:21:49 +00:00
ipc	Bug 1577336: Part 7 - Move DXGI async plugin operations to compositor process r=jmathies,mattwoodrow,sotaro,mccr8	2019-11-20 21:49:35 +00:00
test	Bug 1593170. Skip plugin-background-*-step.html when we do not have the test plugin. r=mattwoodrow	2019-11-18 11:28:02 +00:00