It seems like we need to draw the line somewhere. Otherwise, we'll end up exposing the whole DOM via the WebKit API. Where do you think the optimum cut-off is?
Adam On Tue, Oct 20, 2009 at 1:55 PM, Marshall Greenblatt <magreenbl...@gmail.com> wrote: > Hi All, > > The Chromium WebKit API does not currently provide a wrapper for the > WebCore::Document object associated with a WebCore::Frame. CEF > (http://code.google.com/p/chromiumembedded), which also uses the WebKit API, > would like access to this object at the C++ level. Is there interest in the > broader Chromium community for having a Document wrapper as part of the > WebKit API? > > Thanks, > Marshall > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
