Bug 104204 - [Chromium] Expose layer content opacity query function in WebContentLayerClient API
Summary: [Chromium] Expose layer content opacity query function in WebContentLayerClie...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Justin Novosad
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-05 18:24 PST by Justin Novosad
Modified: 2012-12-05 21:54 PST (History)
9 users (show)

See Also:

Attachments
Patch (5.73 KB, patch)
2012-12-05 18:39 PST, Justin Novosad 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Novosad 2012-12-05 18:24:09 PST 
[Chromium] Expose layer content opacity query function in WebContentLayerClient API
Comment 1 Justin Novosad 2012-12-05 18:39:05 PST 
Created attachment 177903 [details]
Patch
Comment 2 WebKit Review Bot 2012-12-05 18:41:50 PST 
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.
Comment 3 Justin Novosad 2012-12-05 18:44:00 PST 
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!
Comment 4 Dana Jansens 2012-12-05 18:45:05 PST 
Can't you use cc::Layer::contentsOpaque() ? That's where this value comes from.
Comment 5 Justin Novosad 2012-12-05 18:47:33 PST 
(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...