Closed Bug 506220 Opened 15 years ago Closed 14 years ago

java will not load

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mail, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2011-1-30])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2pre) Gecko/20090723 Ubuntu/9.04 (jaunty) Shiretoko/3.5.2pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2pre) Gecko/20090723 Ubuntu/9.04 (jaunty) Shiretoko/3.5.2pre

On older version of mozilla Java crossword loads in but on this version the crossword will not load in. The bottom of the page says that it is "transferring data from adimage.guardian.co.uk" bur=t never gets any further.

Reproducible: Always

Steps to Reproduce:
1.Type in url as above and the page stops with a blank Java background
2.
3.
Actual Results:  
blank grey rectangle

Expected Results:  
blank grey rectangle with J.ava crossword superimposed over it. I still have a working copy of 3.0 and it works fine
I experience nearly the same issue on the URL above. I see a blank space (white, not grey), and the "Transferring data..." message in the status bar. After a while, the status bar changes to "Done.", however.

More crucially, on the web page of my bank (which means I can't access my bank account from Firefox).

Oddly, both pages work without any issues at all in SeaMonkey.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
the condition does not appear to exist in 3.6.13. Guardian crossword loads fine now.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.