Unable to reproduce the issue on the latest canary(63.0.3231.0) and the latest stable(61.0.3163.100) on Windows-10. Not seeing bottom part clipped as shown in the above screenshot.

raymondcamden@: Could you please check the same in new profile or incognito and confirm if this is consistent. Also mention the screen resolution where you are seeing this issue.

Thank you!

Deleted: 771358.png 474 KB

	771358.png 474 KB View Download

I was able to confirm this with an incognito window. One thing I've noticed is that it seems to "add up" over time. For example, in a fresh test, I may only see the bottom part of a g character cropped off. It's very subtle and easy to miss. The more I use this particular app, or if I use Preserve Log, it seems to "add up" over time and get steadily worse. Can you try w/ preserve log? Or if you have an app where you can click to fire off an XHR, maybe that would reveal it?

Thank you for providing more feedback. Adding requester "ajha@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Somehow unable to repro with 'preserve log' checked, as well on the latest canary(63.0.3232.0) of Windows-10.

Could you please provide any such sample page or any such app where this is consistently reproducible to try from our end.

Looping allada@ as well for inputs on this.    

Deleted: 771358_preservelog.png 275 KB

	771358_preservelog.png 275 KB View Download

Sorry to add "noise", but I just wanted to say I'm on the road and may not be able to add more detail till next Friday. It seems to be impacting my desktop and not my laptop so I'm not able to recreate here. 

Thank you for providing more feedback. Adding requester "ajha@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

As per comment #6, waiting for an update from reporter for triaging the issue further.

Hence adding 'Needs-Feedback' label.

Thanks..

Cannot repro as well. Please reopen if there are more details.

As I said - I needed a few days. Kinda surprised it was closed without giving me that time, but ok.

I recorded the video you see here:

https://www.youtube.com/watch?v=-KBd5lFPkwg&feature=youtu.be

As you can see, there is a "tiny" bit of the network item visible. I know it is there because I can mouseover and see the details. While I recorded the video more network requests came in, so I do scroll down a few times, but each time, there is evidence of the issue.

I'm not able to re-open this - can one of yall please do so?

Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Tried a repro of this as per the screen-cast in C#10 but still no luck in reproducing this. Attaching the screen-cast of the same. Removing the Needs-Bisect label as we dont have consistent repro to triage this further and requesting allada@ for help in further debugging.

Deleted: 771358.mp4 4.0 MB

	771358.mp4 4.0 MB View Download

I appreciate Google both re-opening this and trying to test it. Sorry I wasn't able to respond earlier. I'm willing to give up on this as a gremlin perhaps, and even if closed, if someone else runs into it, they can comment. 

Thank you again for trying to help reproduce this.

Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

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

Removing bisect label, since this issue was not reproducible from TE end and requesting  	
Platform>DevTools>Network team for further update on this issue.

Thanks!!

Thanks for the report.  Based upon the screenshots, this looks like it only happens when zoomed.

We're still working on it, but the current workaround is to try Ctrl-0 to reset to default zoom then refresh, or use Ctrl +/- to find a zoom level where this doesn't happen.

This issue has been bothering me for a while too, even with zoom set to default via ctrl-0.  After some tinkering, I think I've figured out what's causing it.  The issue happens when the dev tools window is on my primary monitor (docked or undocked, maximized or not), but not on my secondary monitor (docked or undocked, maximized or not).  My primary monitor is 2560 x 1440 set to 150% scale, while my secondary monitor is 1920 x 1080, set to 100% scale.  I've checked with a co-worker who sees the issue as well, and he has a similar setup (primary at non-100%, secondary at 100%, primary shows issue, secondary doesn't).

Ie. I think the issue may be Windows 10 high-DPI mode, possibly when only one monitor has a non-100% scale, or when they're different or something.  Does this info help someone else reproduce this?

comment #22: Since this ticket was merged into an older one, the progress on the issue is tracked on the other report:  https://crbug.com/723789 

We were able to reproduce this and added a fix that landed in M65+ (currently live on Dev and Canary Channels).  You should be able to see it working if you try out Chrome Canary, please let us know if it doesn't!

If you can wait, M65 will make its way to Beta and then Stable in weeks.  Otherwise, one workaround you can try is to zoom-in DevTools (Ctrl +) and close/reopen DevTools and try to trigger it.