Fix small error in relative bounds calc for Chrome OS only.

Fix small error in relative bounds calc for Chrome OS only.

The new relative bounds calculation code walks up the hierarchy applying
offsets and transforms to convert from the relative coordinates of one
object to the global screen coordinates.

This was broken for an obscure case where one of the parents of a node has
width and height zero because we were calling ComputeLocalNodeBounds on
every ancestor, when it was intended to only be called on the node you're
trying to get the bounds of.

BUG=641574
Committed: https://crrev.com/06342c587b4cdedcf484f2660ea915024c6a4d1c
Cr-Commit-Position: refs/heads/master@{#415461}

[dmazzoni, 2016-08-26 22:29:27]

dmazzoni@chromium.org changed reviewers:
+ aboxhall@chromium.org

[aboxhall, 2016-08-26 22:48:22]

lgtm

Is it possible/simple to write a test for this?

[dmazzoni, 2016-08-30 21:02:50]

Regression test added!

[dmazzoni, 2016-08-30 21:02:52]

The CQ bit was checked by dmazzoni@chromium.org

[dmazzoni, 2016-08-30 21:02:53]

The patchset sent to the CQ was uploaded after l-g-t-m from
aboxhall@chromium.org
Link to the patchset: https://codereview.chromium.org/2285913002/#ps20001
(title: "Add regression test")

[commit-bot: I haz the power, 2016-08-30 21:03:46]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-30 22:27:58]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-08-30 22:29:54]

Description was changed from

==========
Fix small error in relative bounds calc for Chrome OS only.

The new relative bounds calculation code walks up the hierarchy applying
offsets and transforms to convert from the relative coordinates of one
object to the global screen coordinates.

This was broken for an obscure case where one of the parents of a node has
width and height zero because we were calling ComputeLocalNodeBounds on
every ancestor, when it was intended to only be called on the node you're
trying to get the bounds of.

BUG=641574
==========

to

==========
Fix small error in relative bounds calc for Chrome OS only.

The new relative bounds calculation code walks up the hierarchy applying
offsets and transforms to convert from the relative coordinates of one
object to the global screen coordinates.

This was broken for an obscure case where one of the parents of a node has
width and height zero because we were calling ComputeLocalNodeBounds on
every ancestor, when it was intended to only be called on the node you're
trying to get the bounds of.

BUG=641574

Committed: https://crrev.com/06342c587b4cdedcf484f2660ea915024c6a4d1c
Cr-Commit-Position: refs/heads/master@{#415461}
==========

[commit-bot: I haz the power, 2016-08-30 22:29:54]

Patchset 2 (id:??) landed as
https://crrev.com/06342c587b4cdedcf484f2660ea915024c6a4d1c
Cr-Commit-Position: refs/heads/master@{#415461}