Good Build: 63.0.3220.0 
Bad Build:  63.0.3221.0

You are probably looking for a change made after 503164 (known good), but no lat
er than 503165 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
https://chromium.googlesource.com/chromium/src/+log/0beaddc405726742b5545de252e6bf0a2d43edba..efec5839674a3443f4648437c261456dfffc10d1

Suspecting: https://chromium.googlesource.com/chromium/src/+/efec5839674a3443f4648437c261456dfffc10d1

Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

It is possible that my change caused this. I don't have Windows hardware to debug it on. Shift-Tab should be moving focus to the previous input area, so perhaps this is a problem with the area which gets scheduled for repaint when TreeView loses focus.

bsep@: do you happen to have Windows hardware handy?

Tagging with blocker label, please undo if not the case.

Thanks.!

Sure, I'll take a look.

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

commit a7ad077437ea1ae74cf4c19aab93723c7230f7ad
Author: Bret Sepulveda <bsep@chromium.org>
Date: Fri Nov 03 23:00:55 2017

Fix selected rows that scroll in a TreeView having incorrect damage.

When the TreeView scheduled a paint it was using the wrong bounds when
the platform wanted to only highlight the row's text (i.e. on Windows).
This resulted in some areas not being repainted when a long selected row
scrolls to the right (in LTR).

Bug:  779983 
Change-Id: I5210d5337a7ad2a6ae6dbaf85ba2601862c7accd
Reviewed-on: https://chromium-review.googlesource.com/748209
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#513931}
[modify] https://crrev.com/a7ad077437ea1ae74cf4c19aab93723c7230f7ad/ui/views/controls/tree/tree_view.cc

Retested above issue on Windows(7,8,10) OS using latest Canary #64.0.3260.0 and issue is fixed. Kindly review an attached screen cast.

Deleted: Actual.mp4 609 KB

	Actual.mp4 609 KB View Download

M63 Stable promotion is coming soon and your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge to M63 ASAP. Thank you.

This bug requires manual review: M63 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), gkihumba@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Before we approve merge to M63 branch 3239, could you pls confirm change is well baked in Canary and safe to merge to M63?

#10: Yes, I can confirm it's working in Canary. The change is very small and safe to merge imo.

Approving merge to M63 branch 3239 based on comments #6 and #11. Please merge ASAP. Thank you.

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

commit d9ba4ef60ea8ea8e3ef7e7dc6cc2b4ab798014ae
Author: Bret Sepulveda <bsep@chromium.org>
Date: Mon Nov 06 21:05:22 2017

Fix selected rows that scroll in a TreeView having incorrect damage.

When the TreeView scheduled a paint it was using the wrong bounds when
the platform wanted to only highlight the row's text (i.e. on Windows).
This resulted in some areas not being repainted when a long selected row
scrolls to the right (in LTR).

TBR=bsep@chromium.org

(cherry picked from commit a7ad077437ea1ae74cf4c19aab93723c7230f7ad)

Bug:  779983 
Change-Id: I5210d5337a7ad2a6ae6dbaf85ba2601862c7accd
Reviewed-on: https://chromium-review.googlesource.com/748209
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#513931}
Reviewed-on: https://chromium-review.googlesource.com/755517
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/branch-heads/3239@{#396}
Cr-Branched-From: adb61db19020ed8ecee5e91b1a0ea4c924ae2988-refs/heads/master@{#508578}
[modify] https://crrev.com/d9ba4ef60ea8ea8e3ef7e7dc6cc2b4ab798014ae/ui/views/controls/tree/tree_view.cc

Note:
Rechecked the above issue on Beta #63.0.3239.39 on Windows (7,8,10) and fix is working as intended.

Please refer attached screencast

Deleted: Actual Beta.mp4 374 KB

	Actual Beta.mp4 374 KB View Download

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

commit a6d3776aae145775e774979f7226470dbca284a9
Author: Scott Violet <sky@chromium.org>
Date: Mon Nov 20 20:02:29 2017

views: fix bug in tree node bounds calculation

A couple of bounds calculations used bounds().x(). bounds() is
relative to the parent, where as these calculations are meant to be
relative to the tree. So, they shouldn't use bounds().x() and should
instead always be 0 based.

BUG= 779983 
TEST=none

Change-Id: I92ffd99c9c7caef25b06bb7bdf3c05bbae466775
Reviewed-on: https://chromium-review.googlesource.com/777768
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517897}
[modify] https://crrev.com/a6d3776aae145775e774979f7226470dbca284a9/ui/views/controls/tree/tree_view.cc

Is cl listed at #17 need to be merged to M63?

Rechecked the above issue on latest Canary #64.0.3274.0 on Windows (7,8,10) and fix is working as intended.

Please refer attached screencast

Deleted: Actual.mp4 762 KB

	Actual.mp4 762 KB View Download