User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.0.9) Gecko/2009040821 Firefox/3.0.9 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.0.9) Gecko/2009040821 Firefox/3.0.9 Images pasted from clipboard from Firefox show up with incorrect colors. Reproducible: Always Steps to Reproduce: 1. Create new document in another app to paste into (eg word processor) 2. Go to Firefox 3. Go to url http://en.wikipedia.org/wiki/File:Breadth-first-tree.svg 4. Copy the image (ie right-click) 5. Go to the new document 6. Paste Image shows up with colours incorrect.

Checking this using the given image has the same results from Opera, Safari and IE8. Pasting from the clipboard (or just dragging the image directly) into AbiWord or Image Analyzer ( http://meesoft.logicnet.dk/Analyzer/ )shows a black background. Note also when doing a Save Image As.. then opening it in Image Analyzer TWO windows are opened, one being the alpha channel. Clearly the way the converter (used by wikipedia on SVG documents works) is buggy if multiple browsers see the same effect. This makes it invalid here.

I just tested this again using FF 3.5.8 and IE 8.06. I copied this image using both browsers: http://www.dixonautomatic.com/imgs/machines/screwdriving/SD107.gif (in other words, right-clicking and selecting the option to copy the image to the clipboard). When I paste from FF into Windows Paint, the white background is shown black. Pasting from IE it is shown correctly in white. I am not sure of the exact circumstances to reproduce this problem in general, but at least in this instance there is a FF-specific problem. (Also I am not sure that, even if other browsers had the same problem, that necessarily means it is NOT a browser bug.)

Other thoughts... - FF displays these images correctly, but then copies them to the clipboard incorrectly. To me, that indicates there is a FF issue to look into, not a file-encoding issue, since FF gets it right at least once - Even if the problem were caused by some sort of file encoding issue, regardless there is a bad user experience. It could be reasonable for FF to handle a case like that just so things work well for the user. Granted, that might be more of an enhancement than a bug. - I personally run into this issue frequently, and I suspect others do as well, so it does have some value to resolve it. Thanks