Beauregard T. Shagnasty wrote:
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>

This contains the frameset code

<frameset rows="100%,*" border="0">
<frame src="http://www.jtl.us/nlightsweb/lib/renhist.htm";
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?

FWIW, the page (using the frameset) does not print correctly in Firefox,
the Opera browser (V.11.51), and Chromium (V.12.0). This isn't a
SeaMonkey browser issue, rather is the fault of the author's design --
but not exactly the frame.

If you examine the source of the framed page, note that the entire
content is embedded in a single one-cell table. Many browsers have had
difficulty over the years in printing table cells that extend beyond the
boundaries of a printed page. The problem is likely some combination of
using a frame and a single-cell organism. ;-)

Yes, but as I said, once I get down to that framed page it prints fine. It's only when the one-cell page is nested in a frame that the problem arises. This is not a new design, and it's not a new problem.

--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to