| commit | e5ad1cf0775659d2db94a9fd7fe5825453109bba | [log] [tgz] |
|---|---|---|
| author | wangxianzhu <wangxianzhu@chromium.org> | Thu May 05 03:56:55 2016 |
| committer | Commit bot <commit-bot@chromium.org> | Thu May 05 03:58:07 2016 |
| tree | e7ca9238c97b85a88f342360cd6285286845037b | |
| parent | cd3a7885f9c5c7ca6e209142af3f73be6ef5d375 [diff] |
Don't let PaintInvalidationLocationChange shadow other reasons Previously PaintInvalidationLocationChange reason shadowed other paint invalidaiton reasons, confusing debugging paint invalidation. For example, when an object is inserted or becomes visible, its position may also changes from zero to non-zero, and we mark its paint invalidation reason as "location change" instead of "object insertion" or "become visible". This CL not only helps paint invalidation debugging, but also reduces churns in future changes in paint invalidation (especially when we enable paint offset caching). BUG=602068 Review-Url: https://codereview.chromium.org/1951043002 Cr-Commit-Position: refs/heads/master@{#391751}