Lock animated property type of result animation during processing

third_party/WebKit/Source/core/svg/animation/SVGSMILElement.h

Index: third_party/WebKit/Source/core/svg/animation/SVGSMILElement.h
diff --git a/third_party/WebKit/Source/core/svg/animation/SVGSMILElement.h b/third_party/WebKit/Source/core/svg/animation/SVGSMILElement.h
index fb1e6ff7a63a7b71f1fa302dab5932c694bb5bee..e4cc0d7432b6c9e32099aacfd8fb0481c2e10484 100644
--- a/third_party/WebKit/Source/core/svg/animation/SVGSMILElement.h
+++ b/third_party/WebKit/Source/core/svg/animation/SVGSMILElement.h
@@ -110,6 +110,8 @@ public:
 
     virtual void resetAnimatedType() = 0;
     virtual void clearAnimatedType() = 0;
+    virtual void lockAnimatedType() = 0;

[fs, 2016/05/18 16:10:40]

Any particular reason we want these to be virtual? I.e why not just put the flag
in SVGSMILElement and add a method to query it in SVGAnimateElement? (Would make
for a slightly smaller patch, but slightly larger elements granted.)

[davve, 2016/05/19 06:38:49]

It was an attempt at limiting intrusiveness and keeping the lock close to the
actual m_animatedProperty member. But the simplicity of your proposal convinces
me. Patch updated.

+    virtual void unlockAnimatedType() = 0;
     virtual void applyResultsToTarget() = 0;
 
     void connectSyncBaseConditions();