Changes between Version 12 and Version 13 of DOMInJavaScript


Ignore:
Timestamp:
Sep 28, 2012 7:18:02 AM (9 years ago)
Author:
haraken@chromium.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DOMInJavaScript

    v12 v13  
    4343=== Option 2: Wrappers are optional
    4444
    45 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.
     45This 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.
    4646
    4747Pros:
     
    5050Cons:
    5151* 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.
    52 * We need to reserve space for .firstChild, .nextSibling, etc on both WebKit and JavaScript.
     52* We need to reserve space for .nextSibling etc on both WebKit and JavaScript.