Closed
Bug 309036
Opened 19 years ago
Closed 17 years ago
JPEG, GIF, and PNGs are not correctly scaled in <svg:image>
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: christian.balkenius, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4 Bitmapped images included with <svg:image> are scaled as if there was an extra white border of 1 pixel to the right and bottom of the image. This makes the image fade toward white in these directions (This is particularily disturbing when very low resolutiom images are scaled up). For GIFs, this effect changes when the same page is reloaded several times. (This may related to that an image looks the same in JPEG and PNG, but will look very different as a GIF). Reproducible: Always Steps to Reproduce: Example: <image x="10" y="10" width="256" height="256" xlink:href="color.jpg" />
Reporter | ||
Updated•19 years ago
|
Summary: JPEG, GIF, and PNGs are not correctly scaled in <svg:images> → JPEG, GIF, and PNGs are not correctly scaled in <svg:image>
Comment 2•19 years ago
|
||
Christian Balkenius, could you please attach and image and SVG showing the problem to this bug? First attach the image first, point the SVG to the bugzilla attachment, then attach the SVG.
Comment 3•18 years ago
|
||
Could this be caused by https://bugzilla.mozilla.org/show_bug.cgi?id=324698?
Comment 4•18 years ago
|
||
Confirming with Firefox 1.5.0.1. Issue should exist on trunk as well (as there it even happens with an HTML img element now due to bug 324698) but my trunk nightly Firefox build (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060331 Firefox/1.6a1) refuses to show the GIF image elements in the test case at all.
Comment 5•17 years ago
|
||
WFM now in trunk builds.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•