Move popular DOM attributes to prorotype chains

LayoutTests/inspector/console/console-dir-expected.txt

Index: LayoutTests/inspector/console/console-dir-expected.txt
diff --git a/LayoutTests/inspector/console/console-dir-expected.txt b/LayoutTests/inspector/console/console-dir-expected.txt
index 5370e37f2f8e7187d973ce6a0dde49f0ed1e346f..797f720d8905fd837916f94a8d6388091bc3f8f4 100644
--- a/LayoutTests/inspector/console/console-dir-expected.txt
+++ b/LayoutTests/inspector/console/console-dir-expected.txt
@@ -14,7 +14,7 @@ Array[2]
 
 NodeList[1]
     0: html
-    length: 1
+    length: (...)

[haraken, 2013/11/29 04:39:40]

This change looks strange. Looking.

[haraken, 2013/11/29 05:19:49]

Ah, understood. The '(...)' is a link with a 'Invoke property getter' message.
When I click the link, I can see '1'.

c.f.,
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit...

The inspector displays the '(...)' link for all DOM attributes that expose JS
getter/setter. This is weird because we cannot see DOM attribute values without
clicking the link. We're planning to move all DOM attributes to prototype
chains.

My suggestion is:

(1) Land this CL with the '(...)' link.
(2) See performance. If the performance is OK and we decide to keep this CL in
the trunk, fix the inspector UI for DOM attributes.
(3) Move all other DOM attributes.

pfeldman: What do you think?

     __proto__: NodeList console-dir.html:10
 
 XPathResult