Monday, May 20, 2024
 Popular · Latest · Hot · Upcoming
51
rated 0 times [  53] [ 2]  / answers: 1 / hits: 11213  / 11 Years ago, wed, january 22, 2014, 12:00:00

I am aware of two ways of calling the print dialog of browser (I used the Search, of course):




  • document.print()

  • document.execCommand('print', false, null)



What is the difference between them? Support across browsers? Papers, docs or standards? Which is more correct thing to use?



Another question: what is the most straight way to print given part of a webpage? I know we can create new window or iframe to call any of two print methods above. Which one has less pitfalls?


More From » html

 Answers
1

I've tested different ways of printing part of webpage across browsers:
Chrome, Firefox, Opera (12 and new), IE11, 10, 9 and 8. I've tried to create new window, new iframe, or use existing iframe on the page. And then tried .print() and .execCommand('print').



Note: Keep in mind that .print() is called on window, and .execCommand() is called on document.



Code used for testing can be found here



Correct me if my testing code is wrong, I just wanted to find the clearest way to do the job. My conclusions:




  • Opera 12 can not print part of a webpage (?)

  • IEs don't print() iframes and windows, except current window.

  • Calling print() on documents inside iframes or created windows in IEs breaks the print() on current document. Be careful!

  • jQuery plugin printThis uses tricks for IE to do the job, and it just works. The only exception is Opera 12. By the way, this plugin uses print().

  • execCommand('print') works almost everywhere and with any approach (iframes, window). It's not supported by Firefox though.

  • execCommand() returns false if call was unsuccessful, so if you don't want to use plugins and magic tricks, create window or iframe, call execCommand('print') and if it returns false, call print().



One more thing:



Creating an iframe is tricky: you can't access its window or document directly (yes, you have ContentDocument property, which behaves differently across browsers). You should name it and then call window.frames[name] to get window object from that iframe. Do not try to call window.frames(id) - it will return the iframe.


[#48446] Tuesday, January 21, 2014, 11 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
reed

Total Points: 725
Total Questions: 85
Total Answers: 89

Location: Singapore
Member since Sat, Jul 25, 2020
4 Years ago
;