363873 - Transparent PNG as SVG image on Intel Mac not displaying correctly

Status: RESOLVED WORKSFORME

(Core :: SVG, defect)

Description

[Amos Hayes]

Viewing a transparent PNG via <svg:image> has psychedelic results on intel mac. Similar to bug 340028.

Comment 1

[Amos Hayes]

Attachment: Testcase package

Attached a zip containing a testcase plus a screen capture of what it looks like on my intel-based mac.

Comment 2

[bill]

Also occurs with transparent GIF

Comment 3

[Jonathan Watt [:jwatt]]

Is this still a problem after the cairo update?

Comment 4

[Jonathan Watt [:jwatt]]

Brian, could you confirm whether this bug is still present?

Comment 5

[Brian Birtles (:birtles)]

Hi Jonathan, sorry I don't have a Mac. I don't know anything about this bug.

Comment 6

[Jonathan Watt [:jwatt]]

Oops. Sorry Brian, wrong Brian. I meant to CC Brian Ewins. :-)

Comment 7

[bill]

FWIW, I'm not able to reproduce this anymore in FF3.

Comment 8

[Jonathan Watt [:jwatt]]

Okay, great. Since we're not going to fix this on branch, and since we don't know exactly what fixed this, I'll close this bug as worksforme then. If anyone still sees this issue in Firefox 3 beta builds or nightlies, please do reopen the bug.

Comment 9

[Amos Hayes]

This has reared its head again in:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14

but is not a problem in:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b5) Gecko/2008032619 Firefox/3.0b5

Are there still regression fixes happening on Firefox 2?

Comment 10

[Mike Shaver (:shaver emeritus)]

You're saying that it was a new regression in 2.0.0.14, which you don't see in 2.0.0.13?  That's surprising, but if so we should look into it for sure.

Comment 11

[Samuel Sidler (old account; do not CC)]

Comment 8 specifically says we're not going to fix this on branch. Nothing here has regressed on branch. Removing blocking flag.

This will be fixed in Firefox 3 but will not be fixed in Firefox 2.

(And, fwiw, I confirmed that the behavior between 2.0.0.13 and 2.0.0.14 is exactly the same and that this bug is indeed fixed on trunk.)