Closed
Bug 77041
Opened 25 years ago
Closed 25 years ago
Liveconnect does not work for JavaObject
Categories
(Core Graveyard :: Java: OJI, defect)
Tracking
(Not tracked)
People
(Reporter: xiaobin.lu, Assigned: xiaobin.lu)
References
Details
Attachments
(1 file)
|
2.60 KB,
text/html
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT)
BuildID:
This bug is an extension of bug 60018. 60018 got fixed for the MRJ. However,
Liveconnect does not work for JavaObject using Sun's Java Plugin.
Reproducible: Always
Steps to Reproduce:
1. Get the attachment and unzip it. Go to html directory, open the
CherokeeTest.html;
2. Click the button in the html page.
Actual Results: An alert dialog will be poped up and after that some text
should be printed in the page. This works well in Netscape 4.7x browser.
Expected Results: Nothing happens!
| Assignee | ||
Comment 1•25 years ago
|
||
Reassign to myself!
Assignee: edburns → xiaobin.lu
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Liveconnect does not work for JavaObject → Liveconnect does not work for JavaObject
| Assignee | ||
Comment 2•25 years ago
|
||
| Assignee | ||
Comment 3•25 years ago
|
||
Couple of things needs to be clarified:
* Currently there is no way to resolve the Cherokee class, we need to resort
the -Xbootclasspath or -classpath.
To solve this problem, we should assumme the Cherokee class is always in
the same directory as the html file because unlike java applet case which we
can specify a codebase, there is no way to specify the codebase here.
* After that, if you test the testcase, probably crash will happen because
the java plugin side needs a valid URL to work and Java plugin side currently
could not get such information from browser side.
Status: NEW → ASSIGNED
| Assignee | ||
Comment 5•25 years ago
|
||
Mark as duplicate of 77194.
*** This bug has been marked as a duplicate of 77194 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•