[Koha-bugs] [Bug 11014] New: Slip Print Problem in Chrome

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11014

            Bug ID: 11014
           Summary: Slip Print Problem in Chrome
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: Templates
          Assignee: oleonard at myacpl.org
          Reporter: dcook at prosentient.com.au
        QA Contact: testopia at bugs.koha-community.org

Currently, you can print circulation slips in Internet Explorer, Firefox,
Chromium, and probably heaps of other browsers but not Chrome. 

When one goes to print a slip in Chrome, a new browser tab is opened, and the
"printThenClose" javascript initiates a print. However, instead of using the
system dialogue box, it uses a Chrome-specific print preview screen.

Since this preview screen is non-standard, the javascript doesn't even detect
it, and it proceeds to close the window.

(Not the most technical description but that's basically what happens.)

Alas, I can't think of any way of getting around this problem. Some research
suggests that people use timers or keyboard/mouse movement handlers, but none
of those are really optimal strategies for fixing the problem.

Another way of getting around it in Chrome is to open the browser using the
"--args --disable-print-preview" flags. That will use the system dialogue
(which halts the processing of the Javascript and thus the closing of the
window until after the actual print is either initiated or cancelled) instead
of the custom print screen.

However, that might be a lot to ask from a lot of users.

I suppose another idea might be to make the printing happen "silently" but then
you don't get to choose your printer which is also sub-optimal.

At the moment, the easiest thing is just to use a different browser (like
Firefox) for circulation if the library prints slips. But again...not really an
optimal solution to the problem.

Just logging it here anyway.

-- 
You are receiving this mail because:
You are watching all bug changes.