it's already fixed in firefox 46, but firefox 44 and 45 are affected. Regression range (probably bug 1150944): https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=e5746165c704a82fc92d059ef9303562d6b3c886&tochange=5ed72fdd632767e03d6862efd10fc15a34256845 and fixed by bug 1082598: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=d8e260e1535f0ff3877b21d6846380dedf449453&tochange=6630a176477ef903dcf3057db755abc43ba5018d
Created attachment 8719696 [details] Reduced testcase for wrong filling Here's a reduced testcase. ctx.fillStyle = "red"; ctx.beginPath(); ctx.moveTo(0, 0); ctx.lineTo(0, 30); ctx.lineTo(30, 30); ctx.lineTo(30, 30); ctx.lineTo(0, 30); ctx.fill(); In Firefox 44.0.2 on OSX, it fills tetragon (0, 0), (0, 30), (30, 30), (10, 20). This happens only when gfx.canvas.azure.accelerated=true. mattwoodrow, can this be fixed somehow? (turning off Skia or backport bug 1082598 or something...?)
We only have a few weeks left until Firefox 45 ships, I'm not sure we can do much at this point unfortunately. Uplifting a skia update is terrifying, the only option would be to disable skia-gl.
tracking-firefox45: --- → ?
I agree with Matt's risk assessment in comment 3. I might be more inclined to accept it if this was a stability or security problem but it's not. In the meantime anyone experiencing this issue (assuming it's mostly developers) can switch to Developer Edition.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Thanks all. I know little about your risk assessment, but I empathize. This specific problem does impact users (and not just developers), but we can come up with a temporary workaround until 46 ships. Thanks again.
We are going to let it ride the train from 46 then...
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox44: affected → wontfix
status-firefox45: affected → wontfix
tracking-firefox45: ? → -
Resolution: --- → FIXED
(In reply to Sylvestre Ledru [:sylvestre] from comment #6) > We are going to let it ride the train from 46 then... I did do some investigation of this, but the amount of changes to the way Skia handles paths internally were too significant to isolate any easy fix. So I am in agreement in just letting this one slip until 46 comes along.
You need to log in before you can comment on or make changes to this bug.