bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Setting globalCompositeMode to something other than source-over gives wrong results with stroke and fill

NEW
Unassigned

Status

()

Core
Canvas: 2D
6 years ago
6 years ago

People

(Reporter: abhinav.lele, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Reporter)

Description

6 years ago
Created attachment 653182 [details]
compositeTest.zip

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120713224749

Steps to reproduce:

I am trying to render two rectangles with different globalCompositeMode settings. I compared results without just 
1) fill
2) stroke and then fill

On Chrome 18.0.1025.168 (Developer Build 134367 Linux) Ubuntu 12.04
and Firefox 14.0.1


Actual results:

Results for Firefox are inconsistent.
Results for Chrome are consistent


Expected results:

Results should be as shown in Chrome
(Reporter)

Comment 1

6 years ago
small typo 
I compared results with just:

Comment 2

6 years ago
Created attachment 653712 [details]
testcase: compositeTest

I attached your testcases, more easy to test.

Comment 3

6 years ago
Created attachment 653713 [details]
testcase: compositeTest-nostroke

Updated

6 years ago
Component: Untriaged → Canvas: 2D
Product: Firefox → Core
Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Firefox/17.0 (BuidID: 20120820030522)

I can confirm that the results for Firefox are inconsistent when compared to Chrome on Windows, Ubuntu and Mac OS X.

Setting the status of this bug to NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All
Version: 14 Branch → Trunk
(Reporter)

Comment 5

6 years ago
Is this going to fixed??
(Reporter)

Comment 6

6 years ago
Is this going to be fixed??
You need to log in before you can comment on or make changes to this bug.