Flaky tab bounds in Windows tests

[Michael Martis]

Hi all,

I am testing logic that calculates the screen bounds of a web contents.

It does so with something like

web_contents_native_view_top_level_widget->GetClientAreaBoundsInScreen()

(actual code here) which I think is typical.

In tests, I set the web contents bounds with

browser()->window()->SetBounds(...)

(actual code here).

It works for all platforms except Windows, where the actual bounds are sometimes ~8 pixels different than expected. An Example failure is here.

What am I doing wrong?

Thanks for your help with a prickly problem,
Michael.