Javascript "window.print()" doesn't work.

RESOLVED EXPIRED

Status

Core Graveyard
Embedding: GRE Core
--
major
RESOLVED EXPIRED
13 years ago
a year ago

People

(Reporter: George Z., Assigned: dougt)

Tracking

1.7 Branch
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

On Windows, I installed (unzipped) a Mozilla 1.7 release from a .zip package,
and ran the bundled mfcembed.exe app, input "javascript:windows.print()" in the
top URL text field, it successfully printed the loaded page. 

But if I install a Mozilla 1.7 release from a .exe package, copy the
mfcembed.exe app bundled in the .zip package to the GRE directory created by the
1.7 .exe package, it runs successfully. But inputing "javascript:
windows.print()" in the URL text field, it hangs with the "Preparing ..." dialog. 

As "javascript: windows.print()" is a commonly used JavaScript, so I logged it
as a "Major" bug. Any fix or help are appreciated !

Reproducible: Always

Steps to Reproduce:
On Windows:
1. Unzip a Mozilla 1.7 .zip package;
2. Install a Mozilla 1.7 .exe package, which creates a GRE directory under
[Program Files] directory.
3. Copy the bundled mfcembed.exe app in the unzipped Mozilla 1.7 directory to
the GRE directory created by the .exe package;
4. Run the copied mfcembed.exe app, load any URL, input "javascript:
windows.print()" to print the loaded page.

Comment 1

13 years ago
Probably invalid. You spelled it wrong. It should be "javascript:
window.print()", not "javascript: windows.print()". There is no "s".
(Reporter)

Comment 2

13 years ago
Thanks for comments. It was a typo in my description. I did use
"javascript:window.print()", NOT "javascript:windows.print()", and saw the
problem. Any more hints? 

Updated

13 years ago
Version: Trunk → 1.7 Branch

Comment 3

13 years ago
Does the GRE folder already contain a mfcembed.exe? Anyway, why do you want to
copy mfcembed.exe to that folder?
(Reporter)

Comment 4

13 years ago
Hi Frank, 

The GRE folder doesn't contain the mfcembed.exe, I'm not sure why. mfcembed.exe
is only contained in an unzipped Mozilla .zip package. As we want to extend
mfcembed.exe for some more funcationalities and release it as a standalone app
working with both Mozilla .zip and .exe installation, we want to make it work
within the GRE folder. I feel this should be a common case, if we extend
mfdembed.exe, we may not be able to bundle it in a Mozilla distribution.

And it does work well (loading pages correctly) within the GRE folder. But the
problem is Javascript "window.print()" doesn't work, as I reported.

Any more comments?
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.