[layoutng] Bidirectional interoperability between layoutng and legacy layout

[layoutng] Bidirectional interoperability between layoutng and legacy layout

Adds a function canUseNewLayout that determines whether to
use the new code, or fall back to the old layout()
implementation.

This mostly works for now. The main thing that still needs
to be done is to correctly pass down the constraints from
the constraint space. I am planning to use
setOverrideContainingBlockLogical{Width,Height} for that,
but I first have to fix it to not be grid-specific.

Complex constraint spaces will need more thought.

BUG=636993
Committed: https://crrev.com/835274ca627ccc8a2877dca52845180f950cdca9
Cr-Commit-Position: refs/heads/master@{#412815}

[cbiesinger, 2016-08-17 17:59:20]

The CQ bit was checked by cbiesinger@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-17 17:59:45]

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

[cbiesinger, 2016-08-17 18:00:23]

Description was changed from

==========
[layoutng] Bidirectional hosting

BUG=
==========

to

==========
[layoutng] Bidirectional interoperability between layoutng and legacy layout

BUG=636993
==========

[cbiesinger, 2016-08-17 18:00:23]

cbiesinger@chromium.org changed reviewers:
+ eae@chromium.org, glebl@chromium.org, ikilpatrick@chromium.org

[cbiesinger, 2016-08-17 18:02:50]

Description was changed from

==========
[layoutng] Bidirectional interoperability between layoutng and legacy layout

BUG=636993
==========

to

==========
[layoutng] Bidirectional interoperability between layoutng and legacy layout

Adds a function canUseNewLayout that determines whether to
use the new code, or fall back to the old layout()
implementation.

This mostly works for now. The main thing that still needs
to be done is to correctly pass down the constraints from
the constraint space. I am planning to use
setOverrideContainingBlockLogical{Width,Height} for that,
but I first have to fix it to not be grid-specific.

Complex constraint spaces will need more thought.

BUG=636993
==========

[commit-bot: I haz the power, 2016-08-17 19:23:50]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-17 19:23:51]

Dry run: This issue passed the CQ dry run.

[eae, 2016-08-18 02:03:51]

LGTM

[cbiesinger, 2016-08-18 13:34:39]

The CQ bit was checked by cbiesinger@chromium.org

[commit-bot: I haz the power, 2016-08-18 13:34:56]

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-18 13:38:47]

Description was changed from

==========
[layoutng] Bidirectional interoperability between layoutng and legacy layout

Adds a function canUseNewLayout that determines whether to
use the new code, or fall back to the old layout()
implementation.

This mostly works for now. The main thing that still needs
to be done is to correctly pass down the constraints from
the constraint space. I am planning to use
setOverrideContainingBlockLogical{Width,Height} for that,
but I first have to fix it to not be grid-specific.

Complex constraint spaces will need more thought.

BUG=636993
==========

to

==========
[layoutng] Bidirectional interoperability between layoutng and legacy layout

Adds a function canUseNewLayout that determines whether to
use the new code, or fall back to the old layout()
implementation.

This mostly works for now. The main thing that still needs
to be done is to correctly pass down the constraints from
the constraint space. I am planning to use
setOverrideContainingBlockLogical{Width,Height} for that,
but I first have to fix it to not be grid-specific.

Complex constraint spaces will need more thought.

BUG=636993
==========

[commit-bot: I haz the power, 2016-08-18 13:38:48]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-08-18 13:40:45]

Description was changed from

==========
[layoutng] Bidirectional interoperability between layoutng and legacy layout

Adds a function canUseNewLayout that determines whether to
use the new code, or fall back to the old layout()
implementation.

This mostly works for now. The main thing that still needs
to be done is to correctly pass down the constraints from
the constraint space. I am planning to use
setOverrideContainingBlockLogical{Width,Height} for that,
but I first have to fix it to not be grid-specific.

Complex constraint spaces will need more thought.

BUG=636993
==========

to

==========
[layoutng] Bidirectional interoperability between layoutng and legacy layout

Adds a function canUseNewLayout that determines whether to
use the new code, or fall back to the old layout()
implementation.

This mostly works for now. The main thing that still needs
to be done is to correctly pass down the constraints from
the constraint space. I am planning to use
setOverrideContainingBlockLogical{Width,Height} for that,
but I first have to fix it to not be grid-specific.

Complex constraint spaces will need more thought.

BUG=636993

Committed: https://crrev.com/835274ca627ccc8a2877dca52845180f950cdca9
Cr-Commit-Position: refs/heads/master@{#412815}
==========

[commit-bot: I haz the power, 2016-08-18 13:40:46]

Patchset 3 (id:??) landed as
https://crrev.com/835274ca627ccc8a2877dca52845180f950cdca9
Cr-Commit-Position: refs/heads/master@{#412815}