[dev-servo] Moz2d rendering backend

Since webrender is now the default renderer, and is being tested on CI, what should we do with the Azure/Moz2D related code in layout / gfx / compositor? The options are: 1) Fully maintain the Azure rendering path - run CI builds against both Azure and Webrender. 2) Leave the Azure rendering

Re: [dev-servo] Moz2d rendering backend

We'll be tackling Printing improvements in Gecko fairly soon--possibly via Moz2D-> SkiaPDF. It might be good to keep that around and see if Servo printing is advanced by sharing our efforts. --Jet On Mon, Oct 3, 2016 at 4:56 PM, Glenn Watson wrote: > Since webrender is now the default renderer