Closed
Bug 53778
Opened 24 years ago
Closed 24 years ago
Java Applet fails to load twice
Categories
(Core Graveyard :: Java: OJI, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: wwixted1, Assigned: edburns)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m17) Gecko/20000807 Netscape6/6.0b2 BuildID: 2000080712 I'm using the Kavachart Java charting applets in HTML. The first time the page loads the Java applet is loaded and displayed correctly. If I attempt to reload the same page the Java applet does not reload. It is somehow cached in its old state even though the HTML parameters have all changed in the new page when i view source. I can demonstate this if you contact me. Please do (858-452-1471). Name is Bill. Reproducible: Always Steps to Reproduce: 1.Place a kavachart applet on an HTML page with some parameters. 2.Display first time, displays correctly. 3.Change the parameters to the applet. 4.Refresh. 5.The applet is shown in its previous state. It has not been reloaded and does not reflect the new (changed) parameters. Actual Results: The Java applet does not reload and displays old data. Expected Results: Refresh should reload Java applets since they may be driven off of HTML parameters in the page.
Re-assigning to Ed Burns, module owner.
Assignee: drapeau → edburns
Comment 3•24 years ago
|
||
Confirming for edburns to have a look, because otherwise this bug is going to languish for another month. Gerv
Status: UNCONFIRMED → NEW
Ever confirmed: true
Tried this scenario with a simple example. Loaded the applet which takes a background color parameter. After reloading, changed the HTML page to reflect a new color. Reloaded the page. New color shows up. Verified this on WinNT/Win98 with FCs version of JRE (1.3.0_01)
Marking fixed per rpallath's comments.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 6•24 years ago
|
||
yeah, looks good, verified fixed on windows branch build (limbo2)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•