[Webkit-unassigned] [Bug 132950] New: [CANVAS] Strokes do not render correctly when a globalCompositeOperation is in effect

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu May 15 05:32:49 PDT 2014


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

           Summary: [CANVAS] Strokes do not render correctly when a
                    globalCompositeOperation is in effect
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
               URL: http://jsfiddle.net/386sM/5/
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Canvas
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: blambov at google.com


Created an attachment (id=231505)
 --> (https://bugs.webkit.org/attachment.cgi?id=231505&action=review)
Test

Applying a stroke after globalCompositeOperation has been set to destination-in, destination-atop, source-in, source-out or copy does not result in correct rendering.

See the attached file and/or fiddle. It draws pairs of canvases, one doing a stroke, setting compositing, then filling, the other filling, setting the complementing compositing mode, then stroking.

What is the expected behavior?
The pairs should be the same, e.g. stroke, source-in, fill should be the same as fill, dest-in, stroke.

What went wrong?
The stroke doesn't appear to be applied in the destination-in, destination-atop cases and does the wrong thing for source-in, source-out and copy.

The rendering is correct on Opera 12 and Firefox 29 Linux and is also broken on Chrome 34 (https://code.google.com/p/chromium/issues/detail?id=373692). The current Safari output is also badly affected by https://bugs.webkit.org/show_bug.cgi?id=132948 and https://bugs.webkit.org/show_bug.cgi?id=132949.

Safari is broken on both MacOS 10.9.2 (Safari 7.0.3) and iOS 7.1.1.

-- 
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