Well, Alice...That does come as a surprise....."NOT." (That's the 1st time I've used that expression.)

"They" will not repair a basic browser function to operate "normally" & fully?Gee whiz! Maybe it's just too damn hard for "them" & "they've" turned green & are trying to save the planet by not cutting down so many trees?

I can see a heap of users that will migrate to other browsers.Not a good way to keep any new users at all, at all.

I have been complaining about "printing" in Firefox since I first used Phoenix back in Aug 2002. And many of the Bugs that existed back then still aren't fixed, so it's no surprise to me that those two Bugs filed in 2008 & 2009 still haven't been fixed. I spend a lot of time using Print Edit to get around bugs like that; and before Print Edit was available I would "view it in Firefox and then look at the Print Preview - then open IE [or Opera, or Safari] and print the page from there, usually without wasting my time with viewing a Preview - each of them would print it properly without fail". I have always wondered how Firefox ever got to its 20% market share that it once had. Surely not on the (lack of) strength of its ability to print to paper.

Besides using Print Edit, sometimes I save a "page" in MHT format using UnMHT and then print that saved page from Firefox - it the webpage is that important to me to have it on paper.

I honestly believe that Mozilla isn't capable of fixing most of the hundreds of printing bugs in Firefox. Probably the oldest code currently in Firefox, dating back to the mid 90's when Netscape created Navigator. And it seems that any time Mozilla "fixes" or attempts to improve something with regards to printing, a regression appears that isn't always fixed.

I think that Mozilla needs to hire some programmers to write an all new "print module" from a clean sheet of paper, and only have them work on print code, without outside distractions of any of the other projects that Mozilla may be working on. In the time that I have waited for "my pet bugs" to be fixed, Google has hired away some top Mozilla talent and gone on to create a whole damn browser that overtook the Microsoft strange-hold on the web.

I'm not going to leave Firefox, especially for Chrome, over "printing" but I sure as hell don't refer people to using Firefox

A mind is a terrible thing to waste. Mine has wandered off and I'm out looking for it.

LIMPET235 wrote:Well, Alice...That does come as a surprise....."NOT." (That's the 1st time I've used that expression.)

"They" will not repair a basic browser function to operate "normally" & fully?Gee whiz! Maybe it's just too damn hard for "them" & "they've" turned green & are trying to save the planet by not cutting down so many trees?

I can see a heap of users that will migrate to other browsers.Not a good way to keep any new users at all, at all.

Absolutely nuts.

A question? Over the many years I have seen reported bug not get 'fixed' but the code causing them was replaced and the problem went away.

With all, or most, of these 'unfixed printing bugs' you write of - do the errors still happen? Would you care to give Bug numbers?

I ask because I don't do a lot of printing from Firefox but I can not think of a serious problem I have had in years. The only one I can think was the early release of the printing of PDF function was problematic for me. Neither of my sons had any problems.

Maybe I do not understand just what it is that you are trying to print that does not print. Nothing that I do can cause the printing, or not printing, to react as you describe. As best as I can follow what you describe I do not get the same results.