Bug 81401 - [chromium] Animating opacity is not opaque and should create a render surface on main thread
Summary: [chromium] Animating opacity is not opaque and should create a render surface...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Dana Jansens
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-16 14:03 PDT by Dana Jansens
Modified: 2012-03-18 17:58 PDT (History)
6 users (show)

See Also:

Attachments
Patch (3.96 KB, patch)
2012-03-16 14:05 PDT, Dana Jansens 		no flags Details | Formatted Diff | Diff
Patch (4.00 KB, patch)
2012-03-18 16:44 PDT, Dana Jansens 		no flags Details | Formatted Diff | Diff
Show Obsolete (1) 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 Dana Jansens 2012-03-16 14:03:03 PDT 
[chromium] Animating opacity is not opaque and should create a render surface on main thread
Comment 1 Dana Jansens 2012-03-16 14:05:05 PDT 
Created attachment 132373 [details]
Patch
Comment 2 Dana Jansens 2012-03-18 16:40:30 PDT 
This is probably not needed?
a) If we don't have/don't have a render surface on main thread but opposite on impl, it shouldn't hurt anything. We don't commit the surface anyway.
b) We don't depend on a surface on main thread for this anywhere.
Comment 3 Dana Jansens 2012-03-18 16:41:41 PDT 
Oh this does affect paint culling. If we make it own a render surface, then we can do scoped paint culling within the surface.
Comment 4 Dana Jansens 2012-03-18 16:44:47 PDT 
Created attachment 132508 [details]
Patch
Comment 5 WebKit Review Bot 2012-03-18 17:58:48 PDT 
Comment on attachment 132508 [details]
Patch

Clearing flags on attachment: 132508

Committed r111144: <http://trac.webkit.org/changeset/111144>
Comment 6 WebKit Review Bot 2012-03-18 17:58:54 PDT 
All reviewed patches have been landed.  Closing bug.