On Sun, Nov 16, 2008 at 5:33 PM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > > On Nov 16, 2008, at 5:16 PM, Maciej Stachowiak wrote: > >> >> On Nov 16, 2008, at 2:53 PM, Aaron Boodman wrote: >> >>> Hello all, >>> >>> I'd like to run some C++ around the same point as the DOMContentLoaded >>> event is fired. Importantly, I need this to happen *before* the >>> window's onload event fires. >>> >>> FrameLoaderClient::dispatchDidFinishDocumentLoad is usually fired at >>> the right point, but it can sometimes happen after window.onload. >>> Would a patch to add something like >>> dispatchDidHandleDOMContentLoadedEvents to FrameLoaderClient be >>> accepted? Or is there some better way to do what I want? >> >> I believe dispatchDidFinishDocumentLoad() will be called right after the >> DOMContentLoaded event is dispatched. So I don't think a new client >> interface is needed. > > Oops, I didn't read your email thoroughly enough before replying. I think if > the "load" event gets dispatched first sometime, that is likely a bug. I > think moving the dispatchDidFinishDocumentLoad() above the checkCompleted() > may fix it.
Yes, that's exactly the problem. Is it OK to move things around like this? I'm just not sure what the contract that embedders are expecting from this interface is. - a _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
