diff options
| author | ajuma <ajuma@chromium.org> | 2015-05-21 07:30:43 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-05-21 14:31:11 +0000 |
| commit | 04063aa44f0b20829ae07663da96eba19ebe8f38 (patch) | |
| tree | 849007b9601050931b362b1496be4842469f7130 /components/printing/test/print_mock_render_thread.h | |
| parent | 11fb72d750b65fc7ffe8cd37f94090bde0925134 (diff) | |
| download | chromium_src-04063aa44f0b20829ae07663da96eba19ebe8f38.zip chromium_src-04063aa44f0b20829ae07663da96eba19ebe8f38.tar.gz chromium_src-04063aa44f0b20829ae07663da96eba19ebe8f38.tar.bz2 | |
cc: Make re-added animations get pushed to the compositor thread
When a layer with an animation is removed from the tree but later
re-added (this can happen, for example, when an iframe containing
an animation is set to display:none and later set back to
display:block), the animation should continue. Currently, the
animation is prevented from getting re-pushed to the compositor
thread since it already has a start time. This logic used to be
needed to prevent incorrectly re-pushing an animation that had
already been deleted on the compositor thread, but is no longer
needed for that purpose since we now always delete animations on
the main thread before deleting them on the compositor thread.
This CL removes this logic.
BUG=409649
Review URL: https://codereview.chromium.org/1148333002
Cr-Commit-Position: refs/heads/master@{#330938}
Diffstat (limited to 'components/printing/test/print_mock_render_thread.h')
0 files changed, 0 insertions, 0 deletions