Fixing two layout tests on Android broken by enabling virtual-viewport

Fixing two layout tests on Android broken by enabling virtual-viewport

The svg test turned out to simply need a rebaseline as the scrollbars should
no longer show up in layout tests.

The autoresize test was off by 1 pixel. This was happening because in
virtual viewport mode we size the main FrameView's width to the content
size and the height by the aspect ratio. This meant that the height would
have some tiny error in some aspect ratios which would get blown up to a
full pixel when we returned an expandedIntSize in
PageScaleConstraintsSet::mainFrameSize. This is fixed by explicitly setting
the FrameView size equal to the viewport size if the content width matches
the viewport width.

BUG=428189
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=184840

[bokan, 2014-11-04 20:24:56]

bokan@chromium.org changed reviewers:
+ aelias@chromium.org

[bokan, 2014-11-04 20:24:56]

ptal

[aelias_OOO_until_Jul13, 2014-11-04 20:33:49]

On 2014/11/04 20:24:56, bokan wrote:
> ptal

Could you instead change the aspect ratio code to first try to round down if
within an epsilon of the integer?  That's a trick to correct for numerical
problems without resorting to full 0.5-rounding.  The issue doesn't sound
specific to autoresize.

[aelias_OOO_until_Jul13, 2014-11-04 20:36:55]

On second thought, it would be cleaner to bypass the aspect ratio and use
viewportHeight directly if contentWidth == viewportWidth.

[bokan, 2014-11-04 20:54:23]

On 2014/11/04 20:36:55, aelias wrote:
> On second thought, it would be cleaner to bypass the aspect ratio and use
> viewportHeight directly if contentWidth == viewportWidth.

Done.

[aelias_OOO_until_Jul13, 2014-11-04 20:55:00]

lgtm

[bokan, 2014-11-04 20:56:58]

The CQ bit was checked by bokan@chromium.org

[commit-bot: I haz the power, 2014-11-04 20:57:59]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/699253002/20001

[commit-bot: I haz the power, 2014-11-04 22:24:37]

Committed patchset #2 (id:20001) as 184840