Bug 33249 - [Chromium] Expose more APIs to eliminate WebCore usage in Chromium.
Summary: [Chromium] Expose more APIs to eliminate WebCore usage in Chromium.
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit API (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Darin Fisher (:fishd, Google)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-05 23:46 PST by Darin Fisher (:fishd, Google)
Modified: 2010-01-07 00:49 PST (History)
0 users

See Also:


Attachments
v1 patch (10.39 KB, patch)
2010-01-05 23:49 PST, Darin Fisher (:fishd, Google)
abarth: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Fisher (:fishd, Google) 2010-01-05 23:46:05 PST
[Chromium] Expose more APIs to eliminate WebCore usage in Chromium.

Expose:

LogNotYetImplemented.state
GlyphPageTreeNode::treeGlyphPageCount()
WebFrameImpl::liveObjectCount()
Comment 1 Darin Fisher (:fishd, Google) 2010-01-05 23:49:31 PST
Created attachment 45955 [details]
v1 patch
Comment 2 Adam Barth 2010-01-05 23:53:42 PST
Comment on attachment 45955 [details]
v1 patch

Looks reasonable.

The WebKit API has a lot of statics, but I guess there is only one WebKit per process.
Comment 3 Darin Fisher (:fishd, Google) 2010-01-05 23:55:06 PST
> The WebKit API has a lot of statics, but I guess there is only one WebKit per
> process.

Yeah... just like WebCore actually :-)
Comment 4 Darin Fisher (:fishd, Google) 2010-01-07 00:49:39 PST
Landed as http://trac.webkit.org/changeset/52851