| Summary: | [Chromium] Expose layer content opacity query function in WebContentLayerClient API | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Justin Novosad <junov> | ||||
| Component: | New Bugs | Assignee: | Justin Novosad <junov> | ||||
| Status: | RESOLVED INVALID | ||||||
| Severity: | Normal | CC: | abarth, cc-bugs, danakj, dglazkov, fishd, jamesr, senorblanco, tkent+wkapi, webkit.review.bot | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Justin Novosad
2012-12-05 18:24:09 PST
Created attachment 177903 [details]
Patch
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI. FYI The purpose of this change is to allow the compositor to skip the initial layer clear when it is known that the layer contents will be opaque. On various mobile devices this redundant drawRect call is often responsible for more than 25% of total rasterization cost! Can't you use cc::Layer::contentsOpaque() ? That's where this value comes from. (In reply to comment #4) > Can't you use cc::Layer::contentsOpaque() ? That's where this value comes from. Wow, I totally missed that. Thanks. Aborting... |