Re: Print issue in SM
On 2/13/2011 2:37 PM PT, Ray_Net typed: And i don't undertand why a browser can display a page correctly and was unable to copy this into a piece of paper... I'm with you on this, Ray, and I've got no idea why, if SeaMonkey has the date required to display something on the screen, it has to go and get the data a second time to display it on paper.seems just a way to clog up the internet!! This issue needs to be escalated. Is there a main bug report for this old problem? I'd like to see Mozilla developers work on this area more. I let you dream ... developers prefer working on what they prefer :-) :( -- Ants can attack with a grain of rice. --a Malagasy Proverb /\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ /If crediting, then use Ant nickname and AQFL URL/link. ( ) If e-mailing, then axe ANT from its address if needed. Ant is currently not listening to any songs on this computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
On 2/14/2011 7:02 AM PT, Ray_Net typed: This issue needs to be escalated. Is there a main bug report for this old problem? I'd like to see Mozilla developers work on this area more. If a new bug report is submitted or an existing one is found, please post the bug number here. It looks like the following bugs reference at least some part of this problem: 254311 263563 322925 353284 356134 ...and really, just search for print preview, there's more of 'em than I care to list here. Getting a page from the screen to the printer has been an issue for a _long_ time. -JW ... and will never be corrected [sighs] -- Ants can attack with a grain of rice. --a Malagasy Proverb /\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ /If crediting, then use Ant nickname and AQFL URL/link. ( ) If e-mailing, then axe ANT from its address if needed. Ant is currently not listening to any songs on this computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Paul B. Gallagher wrote: Daniel wrote: Paul B. Gallagher wrote: Daniel wrote: Paul, does spoofing your SeaMonkey as FF or IE help the situation?? Dunno, have never tried. How to? Paul, when I examine the header of my message, I can see:- Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11 not Firefox whereas yours has:- Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11 Note the not Firefox on the end of mine. If people go to a website which wants to display itself in a particular way, it will examine the User Agent and look for, in most cases, either MSIE versions of Firefox versions. Yeh, I understand what spoofing is and why people do it. If it doesn't find these option, and some others maybe, it might not display anything or just a plain vanilla versions of the page. By adding the not Firefox at the end, I can bluff servers into thinking I am using Firefox. To add the not Firefox, which is enough to trick most servers, go to the browser, type about:config in the address bar, then type user in the filter bar, double click on general.useragent.extra.seamonkey to edit it and add not firefox (or something similar) at the end. RebootJob done. I took the shortcut of restarting SeaMonkey, not my machine, and the option was set when I returned. But it didn't do a bit of good. SeaMonkey still doesn't know how to print the page in question. So I reset the option. Oh, well. This must be another situation, then. Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Ray_Net wrote: David E. Ross wrote: On 2/11/11 4:10 AM, Daniel wrote: Paul B. Gallagher wrote: snip And i don't undertand why a browser can display a page correctly and was unable to copy this into a piece of paper... I'm with you on this, Ray, and I've got no idea why, if SeaMonkey has the date required to display something on the screen, it has to go and get the data a second time to display it on paper.seems just a way to clog up the internet!! Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
NoOp wrote: On 02/10/2011 07:39 PM, Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Yes, switch to Google Chrome/Chromium to print. Attempting to print that page (an most any web page) in anything Mozilla is akin to spitting into the wind keeping dry. Mozilla (SeaMonkey and FF) has had issues for years with printing; I provided some examples on the dev group/list awhile back was told that it was my OS that was the problem: http://web.archiveorange.com/archive/v/JUslgS4dmgZfEKK87TXI http://groups.google.com/group/mozilla.dev.apps.seamonkey/browse_frm/thread/48fffae1a06d4c58/9bbf55890c22c896?tvc=1#9bbf55890c22c896 So I then switch operating systems (from linux to Win7) and... well you can read the entire thread for the responses. I've also tried printing your web page on SM 2.1x and FF 4.x and it's still the same. Just install Chrome/Chromium and print it from there - you'll save yourself a ton of aggravation the print will work out of the box. Try printing this page with Google Chrome: http://sports.yahoo.com/nhl/standings.html The printout looks _identical_ to SM's printout. -JW ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
J. Weaver Jr. wrote: NoOp wrote: On 02/10/2011 07:39 PM, Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Yes, switch to Google Chrome/Chromium to print. Attempting to print that page (an most any web page) in anything Mozilla is akin to spitting into the wind keeping dry. Mozilla (SeaMonkey and FF) has had issues for years with printing; I provided some examples on the dev group/list awhile back was told that it was my OS that was the problem: http://web.archiveorange.com/archive/v/JUslgS4dmgZfEKK87TXI http://groups.google.com/group/mozilla.dev.apps.seamonkey/browse_frm/thread/48fffae1a06d4c58/9bbf55890c22c896?tvc=1#9bbf55890c22c896 So I then switch operating systems (from linux to Win7) and... well you can read the entire thread for the responses. I've also tried printing your web page on SM 2.1x and FF 4.x and it's still the same. Just install Chrome/Chromium and print it from there - you'll save yourself a ton of aggravation the print will work out of the box. Try printing this page with Google Chrome: http://sports.yahoo.com/nhl/standings.html The printout looks _identical_ to SM's printout. -JW BUT works with IE - I know ..IE is crap :-) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
On 2/13/2011 2:27 AM PT, Daniel typed: And i don't undertand why a browser can display a page correctly and was unable to copy this into a piece of paper... I'm with you on this, Ray, and I've got no idea why, if SeaMonkey has the date required to display something on the screen, it has to go and get the data a second time to display it on paper.seems just a way to clog up the internet!! This issue needs to be escalated. Is there a main bug report for this old problem? I'd like to see Mozilla developers work on this area more. -- When you turn on a light in a room, what happens? Shaw said. The roaches scatter, but the ants keep marching. You can step on them, throw water on them, but they keep on marching. I want ants for my defense. --Willy Shaw /\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ /If crediting, then use Ant nickname and AQFL URL/link. ( ) If e-mailing, then axe ANT from its address if needed. Ant is currently not listening to any songs on this computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Ant wrote: On 2/13/2011 2:27 AM PT, Daniel typed: And i don't undertand why a browser can display a page correctly and was unable to copy this into a piece of paper... I'm with you on this, Ray, and I've got no idea why, if SeaMonkey has the date required to display something on the screen, it has to go and get the data a second time to display it on paper.seems just a way to clog up the internet!! This issue needs to be escalated. Is there a main bug report for this old problem? I'd like to see Mozilla developers work on this area more. I let you dream ... developers prefer working on what they prefer :-) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
J. Weaver Jr. wrote: NoOp wrote: On 02/10/2011 07:39 PM, Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Yes, switch to Google Chrome/Chromium to print. Attempting to print that page (an most any web page) in anything Mozilla is akin to spitting into the wind keeping dry. Mozilla (SeaMonkey and FF) has had issues for years with printing; I provided some examples on the dev group/list awhile back was told that it was my OS that was the problem: http://web.archiveorange.com/archive/v/JUslgS4dmgZfEKK87TXI http://groups.google.com/group/mozilla.dev.apps.seamonkey/browse_frm/thread/48fffae1a06d4c58/9bbf55890c22c896?tvc=1#9bbf55890c22c896 So I then switch operating systems (from linux to Win7) and... well you can read the entire thread for the responses. I've also tried printing your web page on SM 2.1x and FF 4.x and it's still the same. Just install Chrome/Chromium and print it from there - you'll save yourself a ton of aggravation the print will work out of the box. Try printing this page with Google Chrome: http://sports.yahoo.com/nhl/standings.html The printout looks _identical_ to SM's printout. -JW That's a Yahoo programming error. They define the look of the page using a css file restricted to media='screen' and don't define any css styling for 'print'. If you remove the media=screen designation from the html the page previews and prints as per the view on the screen. lj ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
On 2/13/11 1:39 PM, Ant wrote: On 2/13/2011 2:27 AM PT, Daniel typed: And i don't undertand why a browser can display a page correctly and was unable to copy this into a piece of paper... I'm with you on this, Ray, and I've got no idea why, if SeaMonkey has the date required to display something on the screen, it has to go and get the data a second time to display it on paper.seems just a way to clog up the internet!! This issue needs to be escalated. Is there a main bug report for this old problem? I'd like to see Mozilla developers work on this area more. If a new bug report is submitted or an existing one is found, please post the bug number here. -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
David E. Ross wrote: On 2/13/11 1:39 PM, Ant wrote: On 2/13/2011 2:27 AM PT, Daniel typed: And i don't undertand why a browser can display a page correctly and was unable to copy this into a piece of paper... I'm with you on this, Ray, and I've got no idea why, if SeaMonkey has the date required to display something on the screen, it has to go and get the data a second time to display it on paper.seems just a way to clog up the internet!! This issue needs to be escalated. Is there a main bug report for this old problem? I'd like to see Mozilla developers work on this area more. If a new bug report is submitted or an existing one is found, please post the bug number here. It looks like the following bugs reference at least some part of this problem: 254311 263563 322925 353284 356134 ...and really, just search for print preview, there's more of 'em than I care to list here. Getting a page from the screen to the printer has been an issue for a _long_ time. -JW ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Paul B. Gallagher wrote: Daniel wrote: Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Paul, does spoofing your SeaMonkey as FF or IE help the situation?? Dunno, have never tried. How to? Paul, when I examine the header of my message, I can see:- Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11 not Firefox where as yours has:- Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11 Note the not Firefox on the end of mine. If people go to a website which wants to display itself in a particular way, it will examine the User Agent and look for, in most cases, either MSIE versions of Firefox versions. If it doesn't find these option, and some others maybe, it might not display anything or just a plain vanilla versions of the page. By adding the not Firefox at the end, I can bluff servers into thinking I am using Firefox. To add the not Firefox, which is enough to trick most servers, go to the browser, type about:config in the address bar, then type user in the filter bar, double click on general.useragent.extra.seamonkey to edit it and add not firefox (or something similar) at the end. RebootJob done. Others might suggest doing this other waysyour choice. Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Daniel wrote: RebootJob done. Reboot Windows? Not necessary; just close and restart the browser. -- -bts -Given enough coffee, I could rule the world... ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Beauregard T. Shagnasty wrote: Daniel wrote: RebootJob done. Reboot Windows? Not necessary; just close and restart the browser. Would you believe...I thought that was the case but figured no harm done to re-boot. Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Daniel wrote: Beauregard T. Shagnasty wrote: Daniel wrote: RebootJob done. Reboot Windows? Not necessary; just close and restart the browser. Would you believe...I thought that was the case but figured no harm done to re-boot. Actually, restarting the browser is not even necessary. I just ran a test with both Firefox 3.6.13 and SeaMonkey 1.1.18 (wife's app), and in neither case did I have to close or restart/reboot anything. The changes made to the UserAgent string show up immediately after saving the about:config change. Save minutes!! -- -bts -Four wheels carry the body; two wheels move the soul ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Daniel wrote: Paul B. Gallagher wrote: Daniel wrote: Paul, does spoofing your SeaMonkey as FF or IE help the situation?? Dunno, have never tried. How to? Paul, when I examine the header of my message, I can see:- Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11 not Firefox whereas yours has:- Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11 Note the not Firefox on the end of mine. If people go to a website which wants to display itself in a particular way, it will examine the User Agent and look for, in most cases, either MSIE versions of Firefox versions. Yeh, I understand what spoofing is and why people do it. If it doesn't find these option, and some others maybe, it might not display anything or just a plain vanilla versions of the page. By adding the not Firefox at the end, I can bluff servers into thinking I am using Firefox. To add the not Firefox, which is enough to trick most servers, go to the browser, type about:config in the address bar, then type user in the filter bar, double click on general.useragent.extra.seamonkey to edit it and add not firefox (or something similar) at the end. RebootJob done. I took the shortcut of restarting SeaMonkey, not my machine, and the option was set when I returned. But it didn't do a bit of good. SeaMonkey still doesn't know how to print the page in question. So I reset the option. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
On 2/11/11 4:10 AM, Daniel wrote: Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Paul, does spoofing your SeaMonkey as FF or IE help the situation?? Daniel This is NOT a sniffing problem. Spoofing Firefox will not help. I tried spoofing Firefox 3.6.13 without any mention of SeaMonkey in the UA string after removing any cookies that might have been set to indicate a different UA string. Both Print and Print Preview were still bad. This is entirely a problem with either the Print component of Gecko or the Print component of Toolkit. (I'm not sure why there are two such components.) Printing from Gecko-based applications have always been buggy. There are 772 open bug reports on the Core components Print Preview, Printing Output, and Printing Setup. There are 23 open bug reports on the Toolkit component Printing. -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
On 2/12/2011 11:58 AM PT, David E. Ross typed: This is NOT a sniffing problem. Spoofing Firefox will not help. I tried spoofing Firefox 3.6.13 without any mention of SeaMonkey in the UA string after removing any cookies that might have been set to indicate a different UA string. Both Print and Print Preview were still bad. This is entirely a problem with either the Print component of Gecko or the Print component of Toolkit. (I'm not sure why there are two such components.) Printing from Gecko-based applications have always been buggy. There are 772 open bug reports on the Core components Print Preview, Printing Output, and Printing Setup. There are 23 open bug reports on the Toolkit component Printing. Why hasn't printing feature get enough love? Do they think printing isn't that important? -- This is what metaphor is. It is not saying that an ant is an elephant. Perhaps; both are alive. No. Metaphor is saying the ant is an elephant. Now, logically speaking, I know there is a difference. If you put elephants and ants before me, I believe that every time I will correctly identify the elephant and the ant. So metaphor must come from a very different place than that of the logical, intelligent mind. It comes from a place that is very courageous, willing to step out of our preconceived ways of seeing things and open so large that it can see the oneness in an ant and in an elephant. --Natalie Goldberg /\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ /If crediting, then use Ant nickname and AQFL URL/link. ( ) If e-mailing, then axe ANT from its address if needed. Ant is currently not listening to any songs on this computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
David E. Ross wrote: On 2/11/11 4:10 AM, Daniel wrote: Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Paul, does spoofing your SeaMonkey as FF or IE help the situation?? Daniel This is NOT a sniffing problem. Spoofing Firefox will not help. I tried spoofing Firefox 3.6.13 without any mention of SeaMonkey in the UA string after removing any cookies that might have been set to indicate a different UA string. Both Print and Print Preview were still bad. This is entirely a problem with either the Print component of Gecko or the Print component of Toolkit. (I'm not sure why there are two such components.) Printing from Gecko-based applications have always been buggy. There are 772 open bug reports on the Core components Print Preview, Printing Output, and Printing Setup. There are 23 open bug reports on the Toolkit component Printing. I agree I never been able to print correctly some pages using mozilla, netscape, and SM now the problem is present from the beginning. And i don't undertand why a browser can display a page correctly and was unable to copy this into a piece of paper... ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. I went to the page that you indicated was giving you problems and as I almost always do with web pages, I high-lighted only what I would want to print (just the NHL stats) and did a Ctrl C. I then opened an editor and did a Ctrl V and printed the text from the editor. Edit, copy and paste would work just as well. http://sports.yahoo.com/nhl/standings.html I have been doing this for years to save on paper and ink and have found it is particularly helpful using SeaMonkey. I see no sense in printing all the adds and crapola that accompany the data on who knows how many pieces of paper, most of which end up in the waste basket anyway. But as many indicated, SeaMonkey's printing capabilities leave a lot to be desired. Some suggested spoofing the site into thinking that you are running Internet Explorer, bad advice for two reasons: 1 The site may use HTML code that is non standard and would not display properly in SeaMonkey and 2 why encourage site programmers to code only for Internet Explorer? John ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
On 02/10/2011 07:39 PM, Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Yes, switch to Google Chrome/Chromium to print. Attempting to print that page (an most any web page) in anything Mozilla is akin to spitting into the wind keeping dry. Mozilla (SeaMonkey and FF) has had issues for years with printing; I provided some examples on the dev group/list awhile back was told that it was my OS that was the problem: http://web.archiveorange.com/archive/v/JUslgS4dmgZfEKK87TXI http://groups.google.com/group/mozilla.dev.apps.seamonkey/browse_frm/thread/48fffae1a06d4c58/9bbf55890c22c896?tvc=1#9bbf55890c22c896 So I then switch operating systems (from linux to Win7) and... well you can read the entire thread for the responses. I've also tried printing your web page on SM 2.1x and FF 4.x and it's still the same. Just install Chrome/Chromium and print it from there - you'll save yourself a ton of aggravation the print will work out of the box. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
On 02/12/2011 06:29 PM, NoOp wrote: On 02/10/2011 07:39 PM, Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Yes, switch to Google Chrome/Chromium to print. Attempting to print that page (an most any web page) in anything Mozilla is akin to spitting into the wind keeping dry. Mozilla (SeaMonkey and FF) has had issues for years with printing; I provided some examples on the dev group/list awhile back was told that it was my OS that was the problem: http://web.archiveorange.com/archive/v/JUslgS4dmgZfEKK87TXI http://groups.google.com/group/mozilla.dev.apps.seamonkey/browse_frm/thread/48fffae1a06d4c58/9bbf55890c22c896?tvc=1#9bbf55890c22c896 So I then switch operating systems (from linux to Win7) and... well you can read the entire thread for the responses. I've also tried printing your web page on SM 2.1x and FF 4.x and it's still the same. Just install Chrome/Chromium and print it from there - you'll save yourself a ton of aggravation the print will work out of the box. Sorry, forgot to add that here is a link of your web page printed to pdf from chromium: http://img28.imageshack.us/i/job201orgchromiumrhh8ug.pdf/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. You have to work with this situation. Everybody here will told you that IE is crap :-) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Paul, does spoofing your SeaMonkey as FF or IE help the situation?? Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Daniel wrote: Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Paul, does spoofing your SeaMonkey as FF or IE help the situation?? Dunno, have never tried. How to? -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
P.S. If you print preview it on your machine (with or without spoofing), do you have the same problem? -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
Here's one that drives me crazy: http://sports.yahoo.com/nhl/standings.html Yes, I know there are a billion errors on the page, but why can't I get a printout that echoes what gets rendered on the screen? -JW ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
J. Weaver Jr. wrote: Here's one that drives me crazy: http://sports.yahoo.com/nhl/standings.html Yes, I know there are a billion errors on the page, but why can't I get a printout that echoes what gets rendered on the screen? -JW Damn! That's *%*ing awful! It's like the page took a puck to the face! -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
On 2/10/11 7:39 PM, Paul B. Gallagher wrote: This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Although the page does not use tables, this might be another example of Bug #294991. The many nested div blocks might be acting like td blocks nested in tr blocks nested in table blocks for the Print component of Gecko or the Print component of Toolkit. See https://bugzilla.mozilla.org/show_bug.cgi?id=294991. In any case, the page is very poorly composed. It's tag soup (many instances of unnecessary HTML tags). It has 155 XHTML errors and 51 CSS errors. I'm surprised that it can be displayed reasonably well. I'm not entirely surprised that it cannot be printed. -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Print issue in SM
On 2/10/2011 7:39 PM On a whim, Paul B. Gallagher pounded out on the keyboard This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. Regardless of how everyone badmouths IE, it prints. I just tried the link with Chrome and it printed fine there also, even the header. It's ridiculous that this flaw has gone on for years and still remains. I have had to remove FF on way too many client machines because of quirks like this that normal users don't understand and just start using what works. I've been installing Chrome on most of them since it is auto-updating and will update even with a Limited User account. Terry R. -- Anti-spam measures are included in my email address. Delete NOSPAM from the email address after clicking Reply. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Print issue in SM
This goes back all the way to Mozilla, so it may be a W3C compliance issue, but it's annoying nevertheless. On many websites, I can't seem to get a decent printout. For example, my local paper has a searchable obituaries page, and I got 60 hits on my last search, but it would only print the first page. I can see the rest on screen, but I can't get them out on paper. http://www.legacy.com/obituaries/montgomerynews/obituary-search.aspx?page=1affiliateid=2762countryid=1daterange=8stateid=49startdate=20110116enddate=20110210entriesperpage=50 This returns 60 hits, of which the first 50 are displayed, but only seven will print. In fact, in print preview, the first page is the page header with no content, the second page is the first page of content, and the third page is the page footer. That's it. The other 43 hits have vanished. I've tried this with several different printers, including Adobe Acrobat, and they're all the same. Mozilla and SeaMonkey seem to think the second page is 10 feet tall and print only the first 11 inches. Needless to say, it prints fine in Internet Exploiter (except the header page, which is the same in both). Any ideas? I hate wasting ink and paper on ads, and I really hate having to switch browsers whenever I want to print something. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey