Initial implementation of WorkletAnimation

third_party/WebKit/Source/core/dom/Document.cpp

Index: third_party/WebKit/Source/core/dom/Document.cpp
diff --git a/third_party/WebKit/Source/core/dom/Document.cpp b/third_party/WebKit/Source/core/dom/Document.cpp
index da753f36b0ef72d8c75c8306aba50db96130842d..536c81e651bf42cdf96ba38532c3c33ee52d167d 100644
--- a/third_party/WebKit/Source/core/dom/Document.cpp
+++ b/third_party/WebKit/Source/core/dom/Document.cpp
@@ -641,6 +641,7 @@ Document::Document(const DocumentInit& initializer,
           &Document::ElementDataCacheClearTimerFired),
       timeline_(DocumentTimeline::Create(this)),
       pending_animations_(new PendingAnimations(*this)),
+      worklet_animation_controller_(new WorkletAnimationController),

[haraken, 2017/09/08 01:11:23]

Don't you need to take some action when Document is ShutDown()?

For example, cancel all pending / running animations on the WorkletAnimation.

[smcgruer, 2017/09/11 18:19:00]

At the moment, I'm unsure. This was based on PendingAnimations
(https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/animation...),
which does not have any such logic that I'm aware of. I believe the destructors
of the garbage-collected Animations/WorkletAnimation classes are simply meant to
take care of it.

We should understand our own lifecycle better though. I will work on this with
majidvp@ and see if we can get a better answer for you.

       template_document_host_(nullptr),
       did_associate_form_controls_timer_(
           TaskRunnerHelper::Get(TaskType::kUnspecedLoading, this),
@@ -7007,6 +7008,7 @@ DEFINE_TRACE(Document) {
   visitor->Trace(svg_extensions_);
   visitor->Trace(timeline_);
   visitor->Trace(pending_animations_);
+  visitor->Trace(worklet_animation_controller_);
   visitor->Trace(context_document_);
   visitor->Trace(canvas_font_cache_);
   visitor->Trace(intersection_observer_controller_);