Hi Emilio!
> Yeah, I'm to blame for this one... This was one of my very first
> contributions to Servo and I followed what Canvas2D did (which is
> equally broken), and I never got around to clean it up.
> Can't wait to see it going away!
It's normal to follow a existing pattern in the code in
Hi, this plan looks like a great improvement over the current state of
webgl in servo.
> * WebGL commands are currently run in the WR backend thread which could
> be
> bad for UI latency (see https://github.com/servo/webrender/issues/607)
Yeah, thanks for getting rid of this!
> The connection be
Hi,
I would like to work on any GSOC servo project not taken up by anyone. Is
there any such project left?
It will be very helpful if someone can guide me a little.
I am a newbie to open source contributions.
I have a little coding experience in python, but willing to learn anything
in the proc
Hi,
This all sounds very good from a WR perspective, exciting!
I'm glad to hear the synchronization objects in the external image
callback APIs work well, that's great.
I also agree that the remaining flickering is a Servo bug - we shouldn't
be doing extra composites when not required just b
Now that we've fixed most of these I went through it again and checked
stuff. Filtering out scoped style and web components failures we only
have a hundred tests left
I recategorized most of them:
https://gist.github.com/Manishearth/086118c940ff86a6cfc573f53c508279
The major issues right now are
5 matches
Mail list logo
