Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Window.print() issue.

I have used window.print() and window.close() functions for my application to load html page and once it is print, the window close automatically. But with new version (67) the printing details breaks into pieces and align to the left. How to solve that issue?

I have used window.print() and window.close() functions for my application to load html page and once it is print, the window close automatically. But with new version (67) the printing details breaks into pieces and align to the left. How to solve that issue?

All Replies (10)

Hi Dilum2019, what do you mean by "the printing details"? If you view the page in Print Preview, does it show the same problem, or is it specific to the window.print() script function?

Hi Jscher2000 , printing details means the content which I want to print. Preview comes right. But prints gonna align left and break in to words. That issue comes because of the windows.print() not gonna support in newer version

Hi Dilum2019, I'm puzzled why you get a different result between Print Preview and window.print() on the identical content. Can you provide a link to a page demonstrating the problem?

Hi jscher, Please use this link below. it shows my problem.

https://codepen.io/Kasun2019/pen/orzPvE

I see, window.print() somehow captures the state of the document before the CSS is applied, maybe because it triggers on DOMContentLoaded??

By the way, why not use an HTML table for the tabular data?

no i cant use tables on that. can you suggest some patch or some setting on the firefox to overcome the problem??

I think you need to find a way to defer window.print() running until document.load. Maybe in an external script file?

Or the user can print it themselves...

Any suggestions for change some settings on firefox?

Sorry, I looked at the CSS preferences, but nothing leaped out at me as being responsible for whether the script runs before or after the CSS is applied. Maybe you'll see something if you experiment.