Bug 105609 - Implement blend mode for accelerated canvas with Core Graphics
Summary: Implement blend mode for accelerated canvas with Core Graphics
Status: RESOLVED MOVED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Canvas (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.8
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on: 100070
Blocks: 100069
  Show dependency tree / graph
 
Reported: 2012-12-20 20:39 PST by Rik Cabanier
Modified: 2022-07-18 15:19 PDT (History)
8 users (show)

See Also:

Attachments
updated script test (7.93 KB, text/javascript)
2012-12-20 20:39 PST, Rik Cabanier 		no flags Details
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 Rik Cabanier 2012-12-20 20:39:22 PST 
When cgcontext is created with an IOSurfaceRef instead of a CGBitmapContext, certain blend modes either don't work or work incorrectly.
Wrong blend modes: color-burn and color-dodge
Non working mode: hue, color, saturation and luminosity

To reproduce, drop attached file in LayoutTests/fast/canvas/script-tests and run the test.
You can also reproduce by opening ayoutTests/fast/canvas/canvas-blend-solid.html in webkit and make sure that accelerated canvas is enabled in the debug menu.
Comment 1 Rik Cabanier 2012-12-20 20:39:49 PST 
Created attachment 180472 [details]
updated script test
Comment 2 Rik Cabanier 2012-12-20 20:48:12 PST 
Also reported as radar 12922671
Comment 3 Rik Cabanier 2013-02-28 12:01:02 PST 
(In reply to comment #2)
> Also reported as radar 12922671

I attached a small test application that demonstrates the issue
Comment 4 Rik Cabanier 2013-02-28 12:01:20 PST 
(In reply to comment #3)
> (In reply to comment #2)
> > Also reported as radar 12922671
> 
> I attached a small test application that demonstrates the issue

(to the radar bug :-))
Comment 5 Brent Fulgham 2022-07-18 15:18:48 PDT 
<rdar://12922671>
Comment 6 Brent Fulgham 2022-07-18 15:19:57 PDT 
The fix for this issue was outside of the WebKit Open Source project.