[Layout API] Use layoutViewItem() in Document

[Layout API] Use layoutViewItem() in Document

Document::layoutView() is deprecated and being removed soon. The
replacement is Document::layoutViewItem(), which routes methods
through the new block layout API. (See linked crbug for details.)
Several new API methods were added which simply proxy to the
underlying layout object.

As this is a fairly critical class and may show up in automatic
blame lists in the future, I should point out that the layout API
has absolutely no performance penalty. These proxy objects (LayoutItem
and friends) are not ever created at runtime; they disappear completely
during compilation/linking. The underlying code produced is identical
to what was being produced before this CL.

There are no functional changes.

BUG=499321
Committed: https://crrev.com/9639f3cbd3fccd1aeee5c320f56cdfdf023ee99f
Cr-Commit-Position: refs/heads/master@{#404733}

[pilgrim_google, 2016-07-07 20:07:46]

pilgrim@chromium.org changed reviewers:
+ cbiesinger@chromium.org, eae@chromium.org, jsbell@chromium.org

[pilgrim_google, 2016-07-07 20:08:02]

Description was changed from

==========
[Layout API] Use layoutViewItem() in Document

Document::layoutView() is deprecated and being removed soon. The
replacement is Document::layoutViewItem(), which routes methods
through the new block layout API. (See linked crbug for details.)
Several new API methods were added which simply proxy to the
underlying layout object.

As this is a fairly critical class and may show up in automatic
blame lists in the future, I should point out that the block API
has absolutely no performance penalty. These proxy objects (LayoutItem
and friends) are not ever created at runtime; they disappear completely
during compilation/linking. The underlying code produced is identical
to what was being produced before this CL.

There are no functional changes.

BUG=499321
==========

to

==========
[Layout API] Use layoutViewItem() in Document

Document::layoutView() is deprecated and being removed soon. The
replacement is Document::layoutViewItem(), which routes methods
through the new block layout API. (See linked crbug for details.)
Several new API methods were added which simply proxy to the
underlying layout object.

As this is a fairly critical class and may show up in automatic
blame lists in the future, I should point out that the layout API
has absolutely no performance penalty. These proxy objects (LayoutItem
and friends) are not ever created at runtime; they disappear completely
during compilation/linking. The underlying code produced is identical
to what was being produced before this CL.

There are no functional changes.

BUG=499321
==========

[cbiesinger, 2016-07-08 22:13:06]

lgtm

[pilgrim_google, 2016-07-11 13:41:36]

The CQ bit was checked by pilgrim@chromium.org

[commit-bot: I haz the power, 2016-07-11 13:41:50]

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-07-11 15:41:05]

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

[commit-bot: I haz the power, 2016-07-11 15:41:06]

Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[pilgrim_google, 2016-07-11 20:06:01]

The CQ bit was checked by pilgrim@chromium.org

[commit-bot: I haz the power, 2016-07-11 20:06:38]

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-07-11 21:23:39]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-11 21:23:52]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-11 21:26:21]

Description was changed from

==========
[Layout API] Use layoutViewItem() in Document

Document::layoutView() is deprecated and being removed soon. The
replacement is Document::layoutViewItem(), which routes methods
through the new block layout API. (See linked crbug for details.)
Several new API methods were added which simply proxy to the
underlying layout object.

As this is a fairly critical class and may show up in automatic
blame lists in the future, I should point out that the layout API
has absolutely no performance penalty. These proxy objects (LayoutItem
and friends) are not ever created at runtime; they disappear completely
during compilation/linking. The underlying code produced is identical
to what was being produced before this CL.

There are no functional changes.

BUG=499321
==========

to

==========
[Layout API] Use layoutViewItem() in Document

Document::layoutView() is deprecated and being removed soon. The
replacement is Document::layoutViewItem(), which routes methods
through the new block layout API. (See linked crbug for details.)
Several new API methods were added which simply proxy to the
underlying layout object.

As this is a fairly critical class and may show up in automatic
blame lists in the future, I should point out that the layout API
has absolutely no performance penalty. These proxy objects (LayoutItem
and friends) are not ever created at runtime; they disappear completely
during compilation/linking. The underlying code produced is identical
to what was being produced before this CL.

There are no functional changes.

BUG=499321

Committed: https://crrev.com/9639f3cbd3fccd1aeee5c320f56cdfdf023ee99f
Cr-Commit-Position: refs/heads/master@{#404733}
==========

[commit-bot: I haz the power, 2016-07-11 21:26:22]

Patchset 1 (id:??) landed as
https://crrev.com/9639f3cbd3fccd1aeee5c320f56cdfdf023ee99f
Cr-Commit-Position: refs/heads/master@{#404733}

[eae, 2016-07-12 16:25:52]

LGTM