Incomplete Print Jobs Using window.print()

[HugeBob]

Hi All,

Has anyone run across the problem of an incomplete print job when
using the print() method? I've got a page that I want the user to be
able to print. The print link points to window.print(). But, when
the job is done, only a portion of the page is printed. But, on
screen, the complete page is intact. Any ideas as to why this is
happening?

 

[Thomas 'PointedEars' Lahn]

Has anyone run across the problem of an incomplete print job when
using the print() method? I've got a page that I want the user to be
able to print. The print link points to window.print(). But, when
the job is done, only a portion of the page is printed. But, on
screen, the complete page is intact. Any ideas as to why this is
happening?

Perhaps a print stylesheet is in place, in which case what you observe would
work/be borken as designed (and only remotely related to window.print(), if
that). Does the same thing happen when you print using the browser menu?


PointedEars

 

[Jeremy J Starcher]

Hi All,

Has anyone run across the problem of an incomplete print job when using
the print() method? I've got a page that I want the user to be able to
print. The print link points to window.print(). But, when the job is
done, only a portion of the page is printed. But, on screen, the
complete page is intact. Any ideas as to why this is happening?

Ideas -- yea. Accurate or useful ideas? Dunno. Way too much
information not given, including a URL.

Ideas include: Frames. a "print" section in the CSS that hides certain
elements. Light grey on white that shows up a white-on-white on your
print out. PEBCAK.

 

[SAM]

Le 9/10/09 9:03 PM, HugeBob a écrit :

Hi All,

Has anyone run across the problem of an incomplete print job when
using the print() method? I've got a page that I want the user to be
able to print. The print link points to window.print(). But, when
the job is done, only a portion of the page is printed. But, on
screen, the complete page is intact. Any ideas as to why this is
happening?

Which browser ?
Which styles sheet ?

 

[Huge B.]

Le 9/10/09 9:03 PM, HugeBob a écrit :



Which browser ?
Which styles sheet ?

Which Browser: FireFox and IE
Which Style Sheet: One we created
Frames: None

Print previews are also incomplete. It's not a matter of white/light-
gray on white. The content is actually missing. But when the web
app runs, all the content is there.

 

[Thomas 'PointedEars' Lahn]

Which Browser: FireFox and IE
Which Style Sheet: One we created

You will have to come up with something a lot more informative, something
that shows you have done your homework, in order to receive competent help
here. To begin with, you could have named the versions of Firefox (no
second capital `f') and the version of Internet Explorer you have tested
with, and the versions where it failed. You should have at least referred
to a publicly available version of the stylesheet you created by URL, or
posted it here (even though it would probably have been off-topic, someone
one knew the answer could have crossposted with followup to
comp.infosystems.www.authoring.stylesheets, where it would have been on-topic).

Please read and take heed of <http://jibbering.com/faq/#posting> pp. And
avoid switching names if you want to be taken seriously here. In fact,
avoid posting only under nickname to begin with.

Frames: None

Print previews are also incomplete. It's not a matter of white/light-
gray on white. The content is actually missing. But when the web
app runs, all the content is there.

There is increasing indication that this problem has nothing to do with
scripting, and the cause is a print stylesheet instead that declares, for
example, display:none or visibility:hidden for the elements in question.
RTFM, RTFFAQ, STFW.


PointedEars

 

[SAM]

Le 9/17/09 6:09 PM, Thomas 'PointedEars' Lahn a écrit :

There is increasing indication that this problem has nothing to do with
scripting, and the cause is a print stylesheet instead that declares, for
example, display:none or visibility:hidden for the elements in question.

or simply an overflow badcome (not welcome)

RTFM, RTFFAQ, STFW.

WNTW: reuteufeu groum groum ... ?

 

[Huge B.]

You will have to come up with something a lot more informative, something
that shows you have done your homework, in order to receive competent help
here.  To begin with, you could have named the versions of Firefox (no
second capital `f') and the version of Internet Explorer you have tested
with, and the versions where it failed.  You should have at least referred
to a publicly available version of the stylesheet you created by URL, or
posted it here (even though it would probably have been off-topic, someone
one knew the answer could have crossposted with followup to
comp.infosystems.www.authoring.stylesheets, where it would have been on-topic).

Please read and take heed of <http://jibbering.com/faq/#posting> pp.  And
avoid switching names if you want to be taken seriously here.  In fact,
avoid posting only under nickname to begin with.



There is increasing indication that this problem has nothing to do with
scripting, and the cause is aprintstylesheet instead that declares, for
example, display:none or visibility:hidden for the elements in question.
RTFM, RTFFAQ, STFW.

PointedEars

Which Browser: Firefox 3.0.11, IE 6.0.2900.5512

As I'm working in an unusual environment, "publicly available" is not
possible. If it were available, I'd have posted a link to it as well
as the page to begin with. That would have been the simplest thing to
do. And, as for switching names, I haven't any idea as to what you're
talking about. I'm logged into an account through which I post.
Information on that account in not changing. At least not to my
knowledge.