|Summary:||[chromium] Animating opacity is not opaque and should create a render surface on main thread|
|Product:||WebKit||Reporter:||Dana Jansens <danakj>|
|Component:||New Bugs||Assignee:||Dana Jansens <danakj>|
|Severity:||Normal||CC:||backer, enne, jamesr, piman, vollick, webkit.review.bot|
|Version:||528+ (Nightly build)|
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 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 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.