;[EMAIL PROTECTED]>
To: "Pitaga" <[EMAIL PROTECTED]>
Cc: "Darin Adler" <[EMAIL PROTECTED]>;
Sent: Wednesday, June 25, 2008 1:12 PM
Subject: Re: [webkit-dev] DOM tree surgery and DOM tree destruction
>
> On Jun 25, 2008, at 12:16 PM, Pitaga wrote:
>
>>
On Jun 25, 2008, at 12:16 PM, Pitaga wrote:
> Thanks very much for this response.
>
> We (my co-workers and I) want to use WebKit modules selectively,
> without
> running anything like full browser sessions. Over time, we'll do
> this as
> cleanly as we can, taking full advantage of smart poi
l for any further help.
Pitaga
- Original Message -
From: "Darin Adler" <[EMAIL PROTECTED]>
To: "Pitaga" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, June 25, 2008 10:15 AM
Subject: Re: [webkit-dev] DOM tree surgery and DOM tree destruction
> On Jun 25, 2
On Jun 25, 2008, at 10:06 AM, Pitaga wrote:
> For example, suppose that a browser based on WebKit has loaded a Web
> page and parsed it, producing a DOM tree T. As an exercise, I want
> to perform surgery on T and then destroy both T and the constituents
> that the surgery removed from T, wi
Given that Node methods have parameters and return values that are variously
specified to be raw pointers and PassRefPtr's, what's the best practice for DOM
tree surgery? Also, what's the best way to destroy DOM trees and constituents
of DOM trees? I've read the first draft of Darin Adler's "Ref
5 matches
Mail list logo
