http://fynl.free.fr/vrac/imgbug.xml The two image displayed are the same, first is included in normal html way, second as image element in svg included. In my ppc box, svg (cairo 0.20) the colors are not exactly the same, as you can see here: http://fynl.free.fr/vrac/imgbug.png .
How many colours are you using? Is SVG trying to dither down to 256 colours and doing the best it can?
(In reply to comment #1) > How many colours are you using? Is SVG trying to dither down to 256 > colours and doing the best it can? I use 24 bits colors (XFree)
I have nothing nstructive to offer at present at I don't have a lizard with SVG to hand. I will look again in due course, but you may have to wait until someone more versed with SVG happens along
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b) Gecko/20050115 Firefox/1.0+ I compiled Firefox using what I thought were standard methods, and got a crash on the URL given. This is probably something that I am doing wrong.
(In reply to comment #4) > Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b) Gecko/20050115 > Firefox/1.0+ > > I compiled Firefox using what I thought were standard methods, and got > a crash on the URL given. This is probably something that I am doing wrong. I have crash with libart too. This is anyway probably a bug on cairo (endianess), wich is used as renderer in svg native.
OK I will post a stack trace in due course
Created attachment 172491 [details] [diff] [review] nsSVGImageFrame.cpp diff solving the problem This patch is not well written, i am not a dev. But it solves the problem in my ppc/box. Normally the patch should change nothing in little endian. http://lists.freedesktop.org/archives/cairo/2005-January/002624.html for an explanation of ARGB32 cairo format.
Is this fixed now that bug 283092 went in?
(In reply to comment #9) > Is this fixed now that bug 283092 went in? > No. Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.8b2) Gecko/20050326 Firefox/1.0+ Mnenhy/0.7.1 Maybe because of that: +#if defined(XP_UNIX) && !defined(XP_MACOSX) +#define REVERSE_CHANNELS +#endif Probably Linux PPC does not define XP_MACOSX.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Created attachment 199161 [details] svg:image vs html img screenshot confirming this bug as seen on a Sun Ray client, running Sun Solaris 9 on the server-side. I cannot confirm if this is the exact same error, because the linked screenshot gives a 404 error page (this is also the reason why I attached the png screenshot). Testing with a current (20051010) build, so the early version of cairo (0.2) mentioned before is not the cause.
11 years ago
Is this still an issue?
Created attachment 263056 [details] bug still present To answer to comment #13, unfortunatelly the version i use is debian's iceweasel. But, if gecko is the same as in Firefox 2, yes the bug is still present.
I'm interested in official Mozilla trunk builds. The Firefox 2 branch does not have cairo updates, and linux distros are known to build with unsupported versions of cairo anyway. Nevertheless, thanks for checking.
Looks like official mozilla trunk build does not exists for this platform. i found only linux-i686, not linux-ppc.
Need to know if this is still a problem on trunk - renominate if it is.
The link to the testcase is dead. Any chance of an update?