180594 - locks trying to print using web page print buttons

Status: RESOLVED EXPIRED

(Core :: Printing: Output, defect)

Description

[Mike Bray]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1) Gecko/20020826

Have a bug which I cannot find as known

Your comments and suggestions welcome

********

I have found a problem when working with Mozilla 1.1 and
First Direct internet Banking

This is with Mozilla 1.1 under Win98

Problem is lockup when printing

I can print with <ctl-P> but when I try to print with
the <print> <buttons> on the web pages, which is the
only way to print statements, then I get the following
screen which locks.  No further printing at all is possible
until you close Mozilla and restart

Mozilla 0.95 has no such problem

<gif will not insert, but the mozilla <printing> box appears and 
just locks with zero progress on the progess bar>


Reproducible: Always

Steps to Reproduce:
1.
2.
3.




This must be soemthing to do with Mozilla trying to fetch 
the print page, but the banking application is just 
sending once

The printed document {with Mozilla 0.95} never actually 
appears on the screen when the application prints it

*******

I will try to get First Direct to make the "demo" version of 
the banking service make the print buttons live so that 
I can report a method of testing this

Regards

Comment 1

[Olivier Cahagne]

can you try again with latest 1.2 ?
http://ftp.mozilla.org/pub/mozilla/nightly/latest-1.2/

Comment 2

[Mike Bray]

As suggested, tried again with latest build.

This is Mozilla build ID: 2002111512

Mozilla 1.2
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2) Gecko/20021115

*****************

Same problem, but no progress bar.

Exactly what happens is that I get the <Print confirmation screen>, and 
when I OK this, comes up with the Mozilla printing window
Progress: Preparing...

  .... and locks here

Comment 3

[Torben]

Is the printing done from a pop-up window? If so, this is probably the same as
bug 180114.

Comment 4

[Mike Bray]

Have looked at bug 180114
No - not same - but it is probably conflict between some javascript and
how Mozilla handles this.  I will try and get the script from the 
banking software people.

Comment 5

[Mike Bray]

I am very keen to solve this problem
It has become a technical challenge

I have worked out how to see the source code of the page,
and so far I have the source for the frame with the print
button, and in there is the relevant bit ....

***************

<script>function L37()
{return parent.logo.LBFReq("id","","","NAVIGATE","1677","","ALLOWED")};function
P37(){ return parent.logo.mon(this,"print");};</SCRIPT><a NAME="id" class=""
TARGET="app" href="javascript:void(0)" onmouseover="return P37()"
onmouseout="parent.logo.blankStatus();" onblur="parent.logo.blankStatus();"
onfocus="P37()"

onclick=" return L37()">print</a><img src="/images/arrowright.gif"

WIDTH="12" HEIGHT="15" /></td><td height="30"
align="left" width="270" valign="middle"><script>function L38(){return
parent.logo.LBFReq("id","","","NAVIGATE","312","","ALLOWED")};function P38(){
return parent.logo.mon(this,"download");};</SCRIPT>

****************

So I go to the frame named "logo" in the parent to find LBFReq.
This page refers three ".js" files

One of these contains function LBFReq .....

***************

function LBFReq( linkName, linkValue , linkValidate, linkEventId, linkCCid,
linkModifier ,linkAccess)
{
    if ( parent.logo.clicksAllowed == true )
    {
        suppressClicks();
        if( linkAccess!="DENIED")
        {
            waitScripts(linkName, linkValue , linkValidate, linkEventId,
            linkCCid, linkModifier ,linkAccess);
        }
        else
        {
            allowClicks();
            alert('We are unable to action your request at the moment. Please
            try later.');
        };
    }
    return false;
};
function waitScripts( linkName, linkValue , linkValidate, linkEventId,
linkCCid, linkModifier ,linkAccess)
{
    clearTimeout(parent.logo.reqTimer);
    var proc= ( haveScripts() == true) ? "delayedLBFReq" : "waitScripts";
    parent.logo.reqTimer = setTimeout(proc+"('" + linkName + "','" + linkValue
    + "','" + linkValidate + "','" + linkEventId + "','" + linkCCid + "','" +
    linkModifier + "','" + linkAccess + "')",100);
}

***********************************

I have never tried to understand JavaSCripts before, but plan to learn
fast and then I find the problem

If someone could just tell me that I am going the right way please ?

When my brain cools down I will proceed further

Mike Bray

Comment 6

[rods (gone)]

I appreciate the help, I assume you have "Save Page As..." and then saved it
"complete" so it saves all the JS and html?

Comment 7

[simon annear]

Hi Mike

Are you still having printing problems with a recent version of Mozilla ?

Comment 8

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 9

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.