Issue 673134 link

Starred by 0 users

Issue metadata

Status:	Archived
Owner:	█ reve...@chromium.org Last visit > 30 days ago
Closed:	Dec 2016
Cc:	dcasta...@chromium.org █ jbau...@chromium.org
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	3
Type:	Bug
VerifyIn-58 VerifyIn-59 VerifyIn-60 VerifyIn-61

Exo client damage region is not used correctly

Project Member Reported by reve...@chromium.org, Dec 11 2016

Issue description

Exo currently always damages the full surface and ignore the damage region provided by the client.

Comment 1 by reve...@chromium.org, Dec 11 2016

Status: Fixed (was: Assigned)

Project Member

Comment 2 by bugdroid1@chromium.org, Dec 11 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b266b259a929114a39aba840625ce1648feb7dc8

commit b266b259a929114a39aba840625ce1648feb7dc8
Author: reveman <reveman@chromium.org>
Date: Sun Dec 11 01:59:02 2016

exo: Fix handling of pending damage.

Pending damage was ignored prior to this change. Full damage should
be used in lost context situations and client provided damage for
normal commit.

BUG= 673134 
TEST=wayland_motion_events

Review-Url: https://codereview.chromium.org/2565973002
Cr-Commit-Position: refs/heads/master@{#437782}

[modify] https://crrev.com/b266b259a929114a39aba840625ce1648feb7dc8/components/exo/surface.cc