Closed Bug 165570 Opened 23 years ago Closed 14 years ago

Javascript calls Java to set public field does not work

Categories

(Core Graveyard :: Java: Live Connect, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: xiaobin.lu, Unassigned)

Details

Attachments

(2 files)

User-Agent: Mozilla/4.79C-CCK-MCD [en] (X11; U; SunOS 5.8 sun4u) Build Identifier: 20020829 When the page tries to call java to set the public field, it fails. I will attach the java applet code and html page for your guys to test. Reproducible: Always Steps to Reproduce: 1. Open the html page 2. Click "Run" 3. You should see "Test Passed" in the lower textarea. Actual Results: Test failed. Expected Results: Test passed.
Attached file Java Applet code
Attached file Html page
Reassigning to Patrick -
Assignee: rogerl → beard
Status: UNCONFIRMED → NEW
Ever confirmed: true
Xiaobin: nice testcase!!! I have a few questions, however. 1. When I compile the applet, I get a warning: [ ]javac fieldpublic.java Note: fieldpublic.java uses or overrides a deprecated API. Note: Recompile with -deprecation for details. [ ]javac -deprecation fieldpublic.java fieldpublic.java:30: warning: show() in java.awt.Component has been deprecated show(); ^ 1 warning Is that important? 2. When I load the testcase HTML file, I get this error in the JavaScript Console: Error: setTimer is not defined It doesn't seem to be defined anywhere, so I removed it from the <body> onLoad event. That shouldn't matter, should it? 3. When I run the test, this is the output I'm getting in the textarea: ------------------------------------------------------------------------------- Setting public object variable of fieldpublic.java program from JavaScript to "java.awt.Dimension[width=22,height=33]" Reading public object variable value of fieldpublic.java program from JavaScript is "undefined" Comparing values ... STATUS: Public_Object_Field FAILED ------------------------------------------------------------------------------- Is that what you're getting?
The answer to the first question is No, it does not matter The answer to the second question is No, it does not matter either The answer to the third question is YES.
-> default assignee for old netscape assigned bugs.
Assignee: beard → live-connect
Product: Core → Core Graveyard
Firefox code moved from custom Liveconnect code to the NPAPI/NPRuntime bridge a while back. Mass-closing the bugs in the liveconnect component which are likely invalid. If you believe that this bug is still relevant to modern versions of Firefox, please reopen it and move it the "Core" product, component "Plug-Ins".
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: