diff options
author | bokan <bokan@chromium.org> | 2015-07-23 11:54:05 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2015-07-23 18:55:09 +0000 |
commit | f553cb3baec926ac32b65382be88896c9e81a6fa (patch) | |
tree | eea810973d60148c5468cb97f637fceaaa7a51b7 /cc/blink/BUILD.gn | |
parent | 8cdfc496335a58cfb8bdd672c7dce0c23456384b (diff) | |
download | chromium_src-f553cb3baec926ac32b65382be88896c9e81a6fa.zip chromium_src-f553cb3baec926ac32b65382be88896c9e81a6fa.tar.gz chromium_src-f553cb3baec926ac32b65382be88896c9e81a6fa.tar.bz2 |
Make CC scrolling/top-controls unit tests create virtual viewport hierarchy.
These tests were not creating the full inner/page_scale/outer hierarchy. This
is problematic since production code has to check for existence of these
layers, making it more complicated. Also, this means the tests aren't as useful
since they're not running on a layer tree that would be used in the real-world.
This CL converts some of these tests to create the virtual viewport hierarchy,
namely:
Inner-Container
|-Page-Scale
|---Inner-Scroll
|-----Outer-Container
|-------Outer-Scroll
This hierarchy is what is considered "the viewport" and it gets attached to a
root-layer. In production, the root-layer can be the "root transform layer",
used for dev-tools emulation, or the "elastic overscroll layer". In these tests
we create a dummy root-layer. The changes in this CL make it possible to DCHECK
in LayerTreeHostImpl::UpdateViewportContainerSizes for the existence of the
outer viewport without crashing in tests.
BUG=425102
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
Review URL: https://codereview.chromium.org/1251913002
Cr-Commit-Position: refs/heads/master@{#340125}
Diffstat (limited to 'cc/blink/BUILD.gn')
0 files changed, 0 insertions, 0 deletions