Move SVGNames to Python

Source/core/dom/custom/CustomElement.cpp

Index: Source/core/dom/custom/CustomElement.cpp
diff --git a/Source/core/dom/custom/CustomElement.cpp b/Source/core/dom/custom/CustomElement.cpp
index a2a150cc0d57e7c56f0dcd2b9e9b980c99114a42..b4e509df66ed8e2b0fc029a6e358233a30b8022e 100644
--- a/Source/core/dom/custom/CustomElement.cpp
+++ b/Source/core/dom/custom/CustomElement.cpp
@@ -71,7 +71,7 @@ bool CustomElement::isValidName(const AtomicString& name, NameSet validNames)
         DEFINE_STATIC_LOCAL(Vector<AtomicString>, reservedNames, ());
         if (reservedNames.isEmpty()) {
             reservedNames.append(MathMLNames::annotation_xmlTag.localName());
-            reservedNames.append(SVGNames::color_profileTag.localName());
+            reservedNames.append("color-profile");

[eseidel, 2013/10/23 07:17:26]

?

[abarth-chromium, 2013/10/23 17:19:15]

We don't implement the <svg:color-profile> element.  Previously the code what
#if 0 in the in file, which caused the element factory to ignore the name but
SVGNames to include it.

This is the only use of the string in the codebase.  Rather than make the string
appear in SVGNames but not in SVGElementFactory, I thought it would be better to
just use a normal string literal here.  I can add a comment if you think that
would be helpful.  I can also a "omitElementFactory" attribute to the in file to
make the tag appear in SVGNames but not in SVGElementFactory.

             reservedNames.append(SVGNames::font_faceTag.localName());
             reservedNames.append(SVGNames::font_face_srcTag.localName());
             reservedNames.append(SVGNames::font_face_uriTag.localName());