Make 'transform' a presentation attribute on SVG elements

third_party/WebKit/Source/core/svg/SVGElement.h

Index: third_party/WebKit/Source/core/svg/SVGElement.h
diff --git a/third_party/WebKit/Source/core/svg/SVGElement.h b/third_party/WebKit/Source/core/svg/SVGElement.h
index 024ad0ad7c4536f0c6bb19ac62c3d4db42854562..88fe22e9fbf825c8b92ee47d342c27338c38f7f6 100644
--- a/third_party/WebKit/Source/core/svg/SVGElement.h
+++ b/third_party/WebKit/Source/core/svg/SVGElement.h
@@ -74,6 +74,9 @@ class CORE_EXPORT SVGElement : public Element {
   }
   static bool isAnimatableCSSProperty(const QualifiedName&);
 
+  bool hasTransform() const;

[pdr., 2016/11/22 04:02:48]

hasTransform and hasAnimatedLocalTransform are pretty similar. Is there a way to
make their differenced more clear?

[fs, 2016/11/22 13:54:07]

I guess we could consider renaming the "...AnimatedLocal..." methods to be more
about including the "motion transform" contribution.
Another option would be to just fold the "motion transform" application into
these two, and then have a "IncludeMotionTransform" enumeration argument a'la
the ComputedStyle method? (I think that would trade one vcall for another, so
hopefully not an issue from that PoV.)

[fs, 2016/11/22 14:01:24]

(Appears I mistakenly thought one of the "...AnimatedLocal..." methods was
virtual, but that was not the case.)

[fs, 2016/11/22 14:54:35]

PS8 contains something along the lines of the latter suggestion.

+  AffineTransform calculateTransform() const;
+
   enum CTMScope {
     NearestViewportScope,  // Used by SVGGraphicsElement::getCTM()
     ScreenScope,           // Used by SVGGraphicsElement::getScreenCTM()