1362905 - Update webrender to be5a41ece41207d2a81c01e97742d0d5515c97b8

Status: RESOLVED DUPLICATE of bug 1361751

(Core :: Graphics: WebRender, enhancement)

Description

[Jerry Shih[:jerry] (UTC+8) (inactive)]

(In reply to Kartikaya Gupta (email:[e-mail]) from comment #0)
> +++ This bug was initially created as a clone of Bug #1358156 +++
> 
> I'm filing this as a placeholder bug for the next webrender update. I may be
> running a cron script [1] that does try pushes with webrender update
> attempts, so that we can track build/test breakages introduced by webrender
> on a rolling basis. This bug will hold the try push links as well as
> dependencies filed for those breakages, so that we have a better idea going
> into the update of what needs fixing. I might abort the cron job because
> once things get too far out of sync it's hard to fully automate fixing all
> the breakages.
> 
> When we are ready to actually land the update, we can rename this bug and
> use it for the update, and then file a new bug for the next "future update".
> 
> [1]
> https://github.com/staktrace/moz-scripts/blob/master/try-latest-webrender.sh

I'm trying to update the WR to be5a41ece41207d2a81c01e97742d0d5515c97b8, but there are some big changes for the changing of ClipRegion structure and the removing of Auxiliary[1]. I still have the problem for the ClipRegion changing in WR binding code. So, if someone is familiar with the ClipRegion, please take this bug.

[1]
https://github.com/servo/webrender/pull/1181

Comment 1

[Jerry Shih[:jerry] (UTC+8) (inactive)]

CC :kats to check if the updating is already on going.

Comment 2

[Kartikaya Gupta (email:[e-mail])]

Every time I do a WR update I also file a new bug to track the next update. Look for the bug titled "Future webrender update bug". Currently, yes, servo/webrender#1181 is causing a bustage - :gankro is working on a patch for gecko to fix this.