319630 - Some Java applets fail to display in Print Preview or at all (inconsistent)

Status: RESOLVED DUPLICATE of bug 134002

(Firefox :: General, defect)

Description

[Lucius Chiaraviglio]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

At least some Java applets fail to display in Print Preview.  The applets may actually display when you print, but you can't tell from the Print Preview where they are going to appear.


Reproducible: Always

Steps to Reproduce:
1. Make sure that Firefox is version 1.5 real release and that your Java plugin is updated to 1.5.0_06-b05 (the latest as of a few minutes before reporting this bug).
2. Go to http://probes.invitrogen.com/resources/spectraviewer/ and let it load the Molecular Probes Spectra Viewer.
3. Adjust the page setup appropriately:  color printer in Landscape Mode with Legal size paper (otherwise, stuff gets rearranged and/or chopped off due to the size of the things to be printed, even in Internet Explorer).
4. Open Print Preview.
5. Print.


Actual Results:  
The Spectra Viewer Java applet does not appear in the Print Preview window -- instead, a blank space appears (actually, 2 of them on my system, because the web page is a bit too long for just 1 page).


Expected Results:  
The Java applet should appear in the Print Preview on the page that it is actually going to print on paper (under Internet Explorer 6.0 SP2, this does work properly).


Make sure that Firefox is version 1.5 (final release) and that your Java plugin is updated to 1.5.0_06-b05 (the latest as of a few minutes before reporting this bug), or you won't be able to test this at all (you will get a blank space on the normal web browser screen).

Comment 1

[Lucius Chiaraviglio]

It gets worse:  on another computer, even with Firefox and Java updated as specified above and all old versions of Java uninstalled, the Molecular Probes Spectra Viewer Java applet will not display even on the normal Firefox screen (it actually flashes on extremely briefly and then permanently disappears).  The differences between the two computers are that the one on which it displays on the screen and prints properly is newer, running a newer BIDMC ITS image of Windows XP SP2, which never had any Firefox older than 1.5, whereas the old one (where the Java applet will not display) started out with an old BIDMC ITS image of Windows XP SP1 which was then upgraded to SP2, and had Firefox started out on 1.0.something and then upgraded from 1.5 beta1 through 1.5 RC3 and then 1.5 final, and had Java started out on 1.4.2.something and then upgraded.

Internet Explorer 6.0 SP2 displays the Java applet properly on both computers, under all versions of Java tested.

Comment 2

[Lucius Chiaraviglio]

On the computer where the Java applet will not display on the normal Firefox screen, I get a Java icon in the System Tray that persists even after closing Firefox.  I can still double-click on it or right-click on it to display information about it, so it isn't totally hung, but it doesn't want to go away after the web browser that called it closes.  (This does not happen on the computer on which this Java applet displays on the Firefox screen, and this does not happen with Internet Explorer on either computer.)

Comment 3

[zug_treno]

Duplicate of Core bug 134002?

Comment 4

[Lucius Chiaraviglio]

(In reply to comment #3)
> Duplicate of Core bug 134002?

What I saw on the newer computer would qualify as a duplicate of bug 134002, but what I saw on the older computer is different (although possibly related):  the Java applet doesn't even show up on the normal Firefox screen (except for very briefly flashing on and then disappearing).

Comment 5

[Lucius Chiaraviglio]

With Firefox 1.5.0.1, the display of the Molecular Probes spectra viewer in the normal Firefox window now works on the older computer that I reported.  The Print Preview display of this applet is still broken, so the remaining part of this bug now seems to be a duplicate of bug 134002.  (Both computers that I had available to test now seem to act the same with this Firefox version update.)


*** This bug has been marked as a duplicate of 134002 ***