[dom] support iterable<> NodeList

third_party/WebKit/Source/web/WebRuntimeFeatures.cpp

Index: third_party/WebKit/Source/web/WebRuntimeFeatures.cpp
diff --git a/third_party/WebKit/Source/web/WebRuntimeFeatures.cpp b/third_party/WebKit/Source/web/WebRuntimeFeatures.cpp
index 8b5611c9a1ffcdd2882a1eab6ad796da9b8bd04b..95683cc7c48528c6ff08631f3c0b1c4422caf25c 100644
--- a/third_party/WebKit/Source/web/WebRuntimeFeatures.cpp
+++ b/third_party/WebKit/Source/web/WebRuntimeFeatures.cpp
@@ -149,6 +149,11 @@ void WebRuntimeFeatures::enableImageColorProfiles(bool enable)
     RuntimeEnabledFeatures::setImageColorProfilesEnabled(enable);
 }
 
+void WebRuntimeFeatures::enableIterableNodeLists(bool enable)

[jsbell, 2015/10/26 22:53:34]

Why is this necessary?

[caitp (gmail), 2015/10/26 23:11:46]

For procedures like putting something behind a flag, I usually look for similar
CLs doing the same thing, and appropriate the changes. Build worked, so I didn't
question it. Per comments on the other related CL, it's not necessary

[caitp (gmail), 2015/10/27 02:30:58]

Anyways, got rid of this stuff

+{
+    RuntimeEnabledFeatures::setIterableNodeListsEnabled(enable);
+}
+
 void WebRuntimeFeatures::enableMediaPlayer(bool enable)
 {
     RuntimeEnabledFeatures::setMediaEnabled(enable);