[SVG2] css 'outline' property should apply to svg elements

Source/core/rendering/svg/RenderSVGContainer.cpp

Index: Source/core/rendering/svg/RenderSVGContainer.cpp
diff --git a/Source/core/rendering/svg/RenderSVGContainer.cpp b/Source/core/rendering/svg/RenderSVGContainer.cpp
index e95f6c48635c95ca8a3d84196ab5a7920d974340..74a667be8c8e38c0239dcc0eed4ea2a4b8dfbdcd 100644
--- a/Source/core/rendering/svg/RenderSVGContainer.cpp
+++ b/Source/core/rendering/svg/RenderSVGContainer.cpp
@@ -148,11 +148,11 @@ void RenderSVGContainer::paint(PaintInfo& paintInfo, const LayoutPoint&)
     }
 
     // FIXME: This really should be drawn from local coordinates, but currently we hack it
-    // to avoid our clip killing our outline rect.  Thus we translate our
+    // to avoid our clip killing our outline rect. Thus we translate our
     // outline rect into parent coords before drawing.
     // FIXME: This means our focus ring won't share our rotation like it should.
     // We should instead disable our clip during PaintPhaseOutline

[pdr., 2014/05/09 18:56:40]

Does this comment need updating to no longer refer to PaintPhaseOutline?

As an aside, about the two spaces thing above: In schools in the united states,
anyone under about 30yrs (including me) was taught to add two spaces after a
period because it was easier to read on typewriters. This is no longer the case
with modern font rendering, but it's a hard habit to break :) We should
absolutely remove these when we see them, but that's how they crept into the
comments all over.

-    if ((paintInfo.phase == PaintPhaseOutline || paintInfo.phase == PaintPhaseSelfOutline) && style()->outlineWidth() && style()->visibility() == VISIBLE) {
+    if (paintInfo.phase == PaintPhaseForeground && style()->outlineWidth() && style()->visibility() == VISIBLE) {
         IntRect paintRectInParent = enclosingIntRect(localToParentTransform().mapRect(repaintRect));
         paintOutline(paintInfo, paintRectInParent);
     }