cc: Layer that have empty bounds should still have their contentsScale applied in their transforms.

cc: Layer that have empty bounds should still have their contentsScale applied in their transforms.

The change to add contentsScaleX() and contentsScaleY() allows layers to move
between their layer and content space even when they have empty bounds. Now new
code is moving between these spaces by multiplying these scale factors,
regardless of the layer's bounds, and this seems like the correct thing to do.

However, LayerTreeHostCommon is still only applying contentsScaleX|Y() only when
the bounds are not empty. This is inconsistent with other code, and ends up
causing confusion elsewhere, such as in the scrolling and hit testing code.

We remove the if() conditions on the bounds in LTHCommon, so that the transforms
on any layer match the contentsScales on that layer.

Tests:
cc_unittests:LayerTreeHostCommonTest.verifyLayerTransformsInHighDPI
cc_unittests:LayerTreeHostCommonTest.verifyContentsScale

BUG=160834
R=enne


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=167764

[enne (OOO), 2012-11-14 17:23:55]

I like this a lot.  lgtm

[commit-bot: I haz the power, 2012-11-14 18:06:01]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/danakj@chromium.org/11312226/1

[commit-bot: I haz the power, 2012-11-14 23:34:46]

Change committed as 167764