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

commit 319e7548207643dd095d5b948a6c565862c25c47
Author: Erik Luo <luoe@chromium.org>
Date: Fri Dec 29 21:03:12 2017

DevTools: only preserve stripes in Network log when stuck to bottom

Network's row stripes should not flicker in these 2 common cases:
1) User scrolls via wheel/dragging scrollbar
2) Viewport is stuck to the bottom and new rows added above
   (occurs when sorting on column)

In case 1), the first visible row's stripe may change as you scroll,
while in case 2), this can lead to flickering. Today's viewport
covers case 2) but breaks case 1). This CL tightens the condition
so that stripe preservation only applies to one case.

Bug:  797422 
Change-Id: I43f90ca0afec4b3f4f8de9908991e9035bed55c9
Reviewed-on: https://chromium-review.googlesource.com/843474
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Erik Luo <luoe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#526389}
[modify] https://crrev.com/319e7548207643dd095d5b948a6c565862c25c47/third_party/WebKit/Source/devtools/front_end/data_grid/ViewportDataGrid.js

This bug requires manual review: M64 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), kbleicher@(ChromeOS), abdulsyed@(Desktop)

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

What's the impact if we wait until M-65 vs taking this for M64?

This bug affects UX related to stripes flickering while scrolling, so users who rely on consistent striping may continue to experience confusion.

On the other hand, this bug has been around since M58 and as far as I know, there haven't been other crbugs filed.  It would be nice to have in M64, but it's not critical.

Ah got it. Since it's been around M58, let's have it run through regular channels and take it in M65. 

 Issue 807925  has been merged into this issue.