[Webkit-unassigned] [Bug 99119] Implement a non-compositing path for blending

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Feb 10 09:28:57 PST 2014


https://bugs.webkit.org/show_bug.cgi?id=99119





--- Comment #5 from Mihai Tica <mitica at adobe.com>  2014-02-10 09:26:13 PST ---
(In reply to comment #4)
> (From update of attachment 223714 [details])
> I don't think you can simply remove the composited code path.
> 
> If a blended element is on top of anything composited, then the blended element needs to be composited.
> If the blended element is itself composited, then everything under it needs to be composted for blending to work.

Your statements are correct. Both composited and non-composited code paths should be in place. Previous to this, only the composited path was in place, and any blended element would force the creation of a composited layer.

With this patch, this behaviour is altered: if an element with blend-mode has a property, parent or child that forces compositing, the hardware path is followed. Otherwise, the non-compositing implementation in this patch is used.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list