User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:126.96.36.199) Gecko/20061201 Firefox/188.8.131.52 (Ubuntu-feisty) Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:184.108.40.206) Gecko/20061201 Firefox/220.127.116.11 (Ubuntu-feisty) The postscript output and the printout of a page including unbreakable dashes is unreadable, the dash being probably interpreted as 0x11 followed by 0x20. The result is overwritten names and surnames. Reproducible: Always Steps to Reproduce: 1. Go to the web site 2. Print either as a .ps file, or to the printer 3. Enjoy ! Actual Results: Any composed name, thus having a U+2011 char, has its second part of the name pushed away on the printout, making it overwriting the next name, making the printout barely readable and anyway unusable. Expected Results: Well... A regular printout of such a simple list of names :-) The bug has been seen on Firefox 18.104.22.168, 22.214.171.124 and 126.96.36.199. Not seen on Firefox 3 beta.
Not present in nightly - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2008011704 Minefield/3.0b3pre
Ryan, what do you mean by 'nightly' ? The bug is not present on Firefox 3 beta as I said. It is however a fairly annoying problem not to have any stable release that does properly the printing even though the preview is OK.
As I mentioned, I'd be quite ready to fix it myself, it is just that the code is quite big and I'd appreciate an entry point... It seems a problem with the computation of unbreakables.
My apologies Benoît, I guess I missed that part.
Never mind, but should anyone know where to begin, I am ready to tackle this bug... This bug is in the computation of spaces and positions where unbreakable non-space chars lay, it seems.
Benoît, this bug is fixed on the trunk (on the road to Firefox 3). The only fixes landing on the 2.0 branch are stability, security and regression fixes, so if this bug isn't a regression then any patch wouldn't be considered for landing.
Well, this is then a matter of interpretation : Firefox 1.0.8 does not have the same bug, though it has a bug related to the printout of the same page. Is it a regression ? I would say yes as FF 1.0.8's printout is at least readable even though it has a bug. Now, I can well imagine the reasons of your choice, but today I have *no* suitable browser that handles this page that I would be able to advise :-(
Benoît that is a good question. Do you know what the 1.5 branch does?
The 1.0 branch does forget the thing that overwrites in 2.0 or later. The 1.5 branch does exactly the same as 2.0. Strictly speaking I can't really say that this is a regression...
Benoît there is some debate whether any patch for this would be taken, and I have no definitive answer; It would depend on a number of things including the size of the patch, the bug that regressed it, the scope of the changes, whether a driver accepts this is a regression, etc. Sitting against any patch is the fact that it's not a regression from 1.5 and it must be an obscure bug for this to be the first report against it since the release of Fx 1.5 in Nov 2005. If you want to find a regression range, then there are old builds available at http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/ (check the dirs /2004/, /2005/, /2006/). And of course, if you do make a patch then at the minimum you will be able to make your own build with it included and so benefit from the fix :-)
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.