Implement "create an element" when sync for Custom Element V1

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

Index: third_party/WebKit/Source/core/dom/Document.h
diff --git a/third_party/WebKit/Source/core/dom/Document.h b/third_party/WebKit/Source/core/dom/Document.h
index 15dbe5a785f64644026c1faee0e4e9dc66d9f9d3..a6b116f2914c678dbf44f595578821d06df9510c 100644
--- a/third_party/WebKit/Source/core/dom/Document.h
+++ b/third_party/WebKit/Source/core/dom/Document.h
@@ -218,6 +218,9 @@ enum CreateElementFlags {
     CreatedByParser = 1 << 0,
     // Synchronous custom elements flag:
     // https://dom.spec.whatwg.org/#concept-create-element
+    // TODO(kojii): Remove these flags, add an option to HTMLElementFactory

[dominicc (has gone to gerrit), 2016/06/13 07:37:24]

I think we should not let HTMLElementFactory ever queue upgrade because it won't
work with customized built-in elements. None of those call sites pass in "is." I
think it is better if the caller handles it.

If you want to do it this way, can you sketch the API for
HTMLElementFactory::createElement? How do all of the callers pass "is"?

[kojii, 2016/06/13 13:44:31]

I don't have opinions here, just tried to follow your previous advice. "To..."
was inaccurate probably, removed.

Thinking about the refactoring is on my queue, but haven't really spent time on
it yet.

+    // not to queue upgrade, and let parser/DOM methods to upgrade synchronously
+    // when necessary.
     SynchronousCustomElements = 0 << 1,
     AsynchronousCustomElements = 1 << 1,