On 10/10/11 4:33 AM, Paul B. Gallagher wrote: > Oftentimes SM refuses to print an entire HTML document, truncating it at > the bottom of page one even though it goes on much longer. Here's an > example: > > <http://www.nlightsweb.com/lib/renhist.htm>
3 HTML errors > This contains the frameset code > > <frameset rows="100%,*" border="0"> > <frame src="http://www.jtl.us/nlightsweb/lib/renhist.htm"; 140 HTML errors > frameborder="0" /> > <frame frameborder="0" noresize /> > </frameset> > > which makes it misprint. > > But if I right-click in the middle of the text and tell SM to "show only > this frame," I get the nested page, which prints normally: > <http://www.jtl.us/nlightsweb/lib/renhist.htm> > > Setting aside the question of whether this is good or bad design, > shouldn't SM be able to cope? > Problems: * Of course, the HTML errors (noted above) might easily hose a browser's ability to print the page. * A page that does not make effective use of frames or tables should not make any use of either. * Since the days of Netscape Navigator, Gecko-based browsers have always had problems printing, especially when tables are involved. -- David E. Ross <http://www.rossde.com/>. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
