What I called the "cosmetic flaw" seems to be the root cause of the problem:
The part of the browser that is responsible for determining the need for a
page break does this too late. After printing the last full row of the table
the program started printing the side borders of the next row but discovered
that a page break was needed and finished printing the row on the next page.
How the contents of the leftmost cell of that row gets lost (most of the
time) is probably related to the page break determination problem.
Who is responsible for fixing this?
Cheers,
GerryM
"GerryM" wrote:
> Old Pedant in CodingForums.com suggested a work-around: force page breaks
> rather than relying on the browser / window.print / whatever to cause them.
> It worked.
>
> Forcing page breaks also fixed a cosmetic flaw that had always annoyed me:
> the last row of a page was followed by partial cell side borders, and the top
> row of the next page had no cell top borders and only partial cell side
> borders (in addition to having the left-most cell empty most of the time).
>
> The basic problem remains, somewhere.
>
> Thanks,
>
> GerryM
>
> "GerryM" wrote:
>
> > Thanks for the advice. javascript ... oh well.
> >
> > Gerry
> >
> > "Lem" wrote:
> >
> > > GerryM wrote:
> > > > I had no nibbles from the XP Help and Support group so I'm trying it here.
> > > > I'm using XP SP3 and window.print to print a table created in an .asp page
> > > > on an HP5510 printer.
> > > > Except for a little problem with printing tables under window.print the
> > > > printer works fine but I updated the printer driver to the latest version
> > > > anyway. Let me describe the Table Printing Problem in more detail:
> > > >
> > > > Assume I have a table of 156 rows and 2 columns. Using font size 7 pt, a
> > > > page header + a table header + 55 rows are printed (correctly) on the 1st
> > > > page, a page header + 63 rows are printed (correctly) on the second page, and
> > > > a page header + 38 rows are printed on the 3rd page with the following error:
> > > > The entry for the cell in row 1, column 1 (row 119 of the original table) is
> > > > not printed; all other cellls are printed correctly.
> > > >
> > > > Further results: Say I make the font size larger so that only 38 rows of
> > > > the table are printed on the first page. Then, again, the entry in row 1,
> > > > column 1 of the 2nd page (row 39 of the original table) is not printed, and
> > > > incidentally the row 1, column 1 entries of pages 3 and 4 are also not
> > > > printed, while all other table entries are printed ok. This pretty much
> > > > proves to me that it is not some peculiar contents in a specific table cell.
> > > >
> > > > The behavior is not consistent. In other tests, the entry in row 1, column
> > > > 1 of page 2 is not printed; or the entries in row 1, column 1 of pages 2 and
> > > > 3, are not printed. But in all cases, the remaining entries on those pages
> > > > are printed ok.
> > > >
> > > > Is window.print somehow corrupted? What is going on, and how can I fix it?
> > > >
> > > > Thanks, Gerry
> > >
> > > Try again.
> > >
> > > The "windowsxp.help_and_support" newsgroup actually is about the Windows
> > > XP Help & Support facility -- and not for actual help or support.
> > >
> > > "Window.print" is a JavaScript function. Although it's possible that
> > > someone in a newsgroup focused on printing and faxing problems in
> > > Windows XP might know something about JavaScript, you're more likely to
> > > find help at one of the groups listed here:
> > > http://www.google.com/#hl=en&source=...ipt+help+forum
> > > http://www.google.com/#hl=en&q=javas...help+newsgroup
> > >
> > > --
> > > Lem
> > >
> > > Apollo 11 - 40 years ago:
> > > http://www.nasa.gov/mission_pages/ap...0th/index.html
> > > .
> > >
Similar Threads
Linear Mode
