page does not get displayed

RESOLVED WORKSFORME

Status

--
major
RESOLVED WORKSFORME
16 years ago
14 years ago

People

(Reporter: REUDBVUKSCZE, Assigned: asa)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
User-Agent:       
Build Identifier: 1.3 Beta

The above page does not get displayed. I use Java 1.4.1_01. The page works fine
in Opera 7 and IE 6 SP1, with the same Java plugin.

Reproducible: Always

Steps to Reproduce:
1. Open the web site.
Actual Results:  
Nothing is displayed.

Expected Results:  
Page should get displayed.
Do you need to login to see the empty page ?
if not : wfm with win2k vuild 20030215..
(Reporter)

Comment 2

16 years ago
No, no need to login.
Does not work on Win Me and Win XP, tested it myself.

Maybe it's a problem with Mozillas API to the Java Plugin?

Comment 3

16 years ago
wfm with win98 Build ID 2003021604.
Have Java 1.3.1, but java isn´t needed on this site?

Site is rendering fine in NS4.79, but not in mozilla.
Compare http://www.vr-ebanking.de/demo/index.html
(Reporter)

Comment 4

16 years ago
I have no clue what it could be.

I have this problem with Windows Me and Windows XP, both times I use Mozilla 1.3
Beta.

I do not use any proxy, nor any other software between Mozilla and the Internet...
Have you tried to clear the disk cache ?
(Reporter)

Comment 6

16 years ago
Tried it, but does not work :(

Comment 7

16 years ago
worksforme, but the server is very slow...
(Reporter)

Comment 8

16 years ago
It was my fault, sorry... disabling the User Agent in Mozilla was not a good
idea :))
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED

Comment 9

16 years ago
Nothing was fixed or broken.  Reopening to resolve correctly.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---

Comment 10

16 years ago
-> WORKSFORME as per comment 8.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago16 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.