Changes between Version 12 and Version 13 of DOMInJavaScript

Timestamp:

Sep 28, 2012 7:18:02 AM (12 years ago)

Author:

haraken@chromium.org

Comment:

--

DOMInJavaScript

@@ -43 +43 @@
 === Option 2: Wrappers are optional
 
-This approach creates wrappers only for DOM objects that are touched by JS, as is done in the current JSC/V8 + WebKit. As a fast path, in a case where a wrapper exists, .nextSibling is realized by normal JavaScript property access. As a slow path, in a case where a wrapper object does not exist, .nextSibling is realized by Node::nextSibling() as is done in the current WebKit.
+This approach creates wrappers only for DOM objects that are touched by JS, as is done in the current JSC/V8 + WebKit. As a fast path, in a case where a wrapper exists, .nextSibling is realized by normal JavaScript property access. As a slow path, in a case where a wrapper does not exist, .nextSibling is realized by Node::nextSibling() as is done in the current WebKit.
 
 Pros:
@@ -50 +50 @@
 Cons:
 * GC is not simplified. Since some tree edges are represented in the JS side and other tree edges are represented in the WebKit side, GC still needs to transfer information between a JS engine and WebKit.
-* We need to reserve space for .firstChild, .nextSibling, etc on both WebKit and JavaScript.
+* We need to reserve space for .nextSibling etc on both WebKit and JavaScript.