Closed Bug 209652 Opened 22 years ago Closed 20 years ago

Java AppletContext.showDocument() does nothing

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: tk, Assigned: joshua.xia)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030616 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030616 This line of code displays the given URL in Mozilla 1.1, Netscape 6.2 with Java plug-in version 1.4.1_01. applet.getAppletContext().showDocument(new java.net.URL("file:///d:/abc.html")); In the newest Mozilla (nightly build of today) and in the release candidat 1 it just does nothing. If "file://" is replaced by "http://" then it works. Reproducible: Always Steps to Reproduce: 1. Write a test applet. 2. Include this line applet.getAppletContext().showDocument(new java.net.URL("file:///d:/abc.html")); 3. run the applet in Mozilla Actual Results: The applet is still running. Expected Results: Show the given URL in the main window
-->OJI
Assignee: joe.chou → joshua.xia
Component: Java APIs to WebShell → OJI
QA Contact: avm → dsirnapalli
Whith this configuration, windows 2000, Java plug-in version 1.4.2 and mozilla 1.3 this bug doesn't appear. This bug appears whith mozilla 1.4 and 1.5b. You can verify this at http://denis.apparicio.free.fr/mozilla/index.htm
We tried this for several combinations on Windows 2000. This bug appears in Java 1.3.1, 1.4.1, 1.4.2, 1.5Beta and with Mozilla Versions 1.6 and 1.7rc1 and FireFox 0.8 This is very unpleasant bug, as we are now required to use IE for full functionality of our Applets.
I tested a little more and found out this is not a bug but a feature :-) I recognized a Security Error in the JavaScript console and found the following in the release notes of mozilla: For security reasons, Mozilla does not allow web content to link to local files. An error like:Security Error: Content at url may not load or link to file:///something will appear in the javascript console. If you need to follow links to local paths it is recommended that you drag the link to the location bar and then drop it on the webpage. If you really don't like the security check and are willing to risk all files on your system and that your system can access then you may add the following line to user.js in your personal profile directory. user_pref("security.checkloaduri", false); (Bug 84128) If setting this property to false the file-protocol works as intended.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.