Move popular DOM attributes to prorotype chains

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

 CONSOLE MESSAGE: line 9: test1,test2
 CONSOLE MESSAGE: line 10: [object NodeList]
 CONSOLE MESSAGE: line 11: [object XPathResult]
 CONSOLE MESSAGE: line 21: [object Object]
 Tests that console logging dumps proper messages.
 
 
 
 Array[2]
     0: "test1"
     1: "test2"
     length: 2
     __proto__: Array[0] console-dir.html:9
 
 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
     booleanValue: [Exception: TypeError]
     invalidIteratorState: false
     numberValue: [Exception: TypeError]
     resultType: 4
     singleNodeValue: [Exception: TypeError]
     snapshotLength: [Exception: TypeError]
     stringValue: [Exception: TypeError]
     __proto__: XPathResult console-dir.html:11
 
 Object
     "": ""
     "  ": "  "
     " a b ": " a b "
     $foo5_: 0
     "a↵↵b↵c": "a↵↵b↵c"
     c d: "c d"
     negZero: -0
     __proto__: Object console-dir.html:21