On Tue, Oct 4, 2016 at 7:24 PM, Jet Villegas wrote:
> On Tue, Oct 4, 2016 at 1:33 PM, Jeff Muizelaar
> wrote:
> >
> > I think it would probably make sense for Servo to move printing over to
> > using webrender display items. I feel like that's what Gecko would
> probably
> > prefer to do in the
On Tue, Oct 4, 2016 at 1:33 PM, Jeff Muizelaar
wrote:
> On Mon, Oct 3, 2016 at 7:56 PM, Glenn Watson
> wrote:
>
> > 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 option
Thanks everyone! Based on the feedback, I've submitted a PR to do this:
https://github.com/servo/servo/pull/13590
Feel free to leave comments on it.
Patrick
On Thu, Sep 29, 2016 at 6:26 PM, Patrick Walton wrote:
> Hi,
>
> Given stshine's fantastic work implementing flexbox, I'm wondering wheth
On Mon, Oct 3, 2016 at 7:56 PM, Glenn Watson
wrote:
> 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 a
Yes, that's correct.
On 05/10/16 06:04, Jack Moffitt wrote:
My preference is to remove the azure code from git - it seems unlikely we'll
be working on printing any time soon, and we will always have the history in
git.
This is my preference as well. I think when we want to work on
printing, the
> My preference is to remove the azure code from git - it seems unlikely we'll
> be working on printing any time soon, and we will always have the history in
> git.
This is my preference as well. I think when we want to work on
printing, there may be better ways than what we have now anyway. I
thi
6 matches
Mail list logo
