GitLab

Since page scale factor should never be non-1.f for OOPIFs, and since
we're seeing this happen anyways, this CL inserts some diagnostic checks
to try and determine where in the page-scale-factor pathways the non-1.f
values are originating.

Bug: 845097
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I1d87e3a618d2fd71aa14cc5149084b08ddb7bf14
Reviewed-on: https://chromium-review.googlesource.com/1110345
Commit-Queue: James MacLean <wjmaclean@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569385}