Add CustomElementState for Custom Elements v1

third_party/WebKit/Source/core/dom/Element.h

Index: third_party/WebKit/Source/core/dom/Element.h
diff --git a/third_party/WebKit/Source/core/dom/Element.h b/third_party/WebKit/Source/core/dom/Element.h
index 00be11809ab11b221ac00349b80bebabafb2be6c..5b3f395b44efe884431ca7c02c4a0f0e54b7f59e 100644
--- a/third_party/WebKit/Source/core/dom/Element.h
+++ b/third_party/WebKit/Source/core/dom/Element.h
@@ -374,6 +374,7 @@ public:
     void setIsInCanvasSubtree(bool value) { setElementFlag(IsInCanvasSubtree, value); }
     bool isInCanvasSubtree() const { return hasElementFlag(IsInCanvasSubtree); }
 
+    bool isDefinedCustomElement() const { return getCustomElementState() != CustomElementState::Undefined; }

[dominicc (has gone to gerrit), 2016/05/18 07:56:21]

I wouldn't consider <button> to be a defined *custom* element; does the spec
have something to say about this?

[kojii, 2016/05/18 08:32:15]

Does "isDefinedElement()" look better?

The spec says:
| An element whose custom element state is "uncustomized" or "custom" is said to
be "defined"

isDefinedElement()
isDefinedCustomElementState()
isCustomElementStateDefined()

isDefinedElement() is probably more accurate spec-wise.

     bool isUpgradedV0CustomElement() { return getV0CustomElementState() == V0Upgraded; }
     bool isUnresolvedV0CustomElement() { return getV0CustomElementState() == V0WaitingForUpgrade; }