http://bugzilla.mozilla.org/show_bug.cgi?id=87088

I have a xul file registered as a chrome. In this xul file I have an applet.
When I invoke moz(v0.9.1) with 
mozilla -console -chrome chrome://appletInChrome/content/appletInChrome.xul
The java plug-in(v1.3.1) reports

java.net.MalformedURLException: unknown protocol: chrome



------- Additional Comments From   xxxxx@xxxxx   2001-06-21 08:15 -------

java.net.MalformedURLException:unknown protocol: chrome
at java.net.URL <init>(URL.java:480)
at java.net.URL <init>(URL.java:376)
at java.net.URL <init>(URL.java:330)
at.sun.plugin.navig.win32.PluginObject.setDocumentURL

I tried specifing the applet with both html:applet and html: customer  tags
although I need liveconnect so due to other LC bugs  customer  using applet tag.

<!---
<html:APPLET name="DynamicDocCom" 
code="DynamicDocCom" 

archive="dynamicdoccom.jar, weblogic.jar, xerces.jar" 
width="1"
height="1" 
id="com"
codebase="http://www.hitrun.net"
MAYSCRIPT="true"> <html:param   name="param1"	 value="file:///platform.cfg"/> <html:param   name="param2" 	value="file:///generic.cfg"/> <html:param   name="param3"	 value="alerts"/> <html:param   name="param4" 	value="beatest1"/> </html:APPLET> -->
OBJECT TAG
<html: customer 
classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
id="com"
width="1"
height="1"
archive="dynamicdoccom.jar,weblogic.jar, xerces.jar"
name="DynamicDocCom" 
code="DynamicDocCom"
>

<html:param name="type" value="application/x-java-applet;version=1.3"/>
<html:param name="codebase" value="http://www.hitandrun.net"/>
<html:param name="scriptable" value="true"/>
<html:param name="mayscript" value="true"/>
</html: customer >



------- Additional Comments From   xxxxx@xxxxx   2001-06-27 18:22 -------

This is a very interesting bug.  Please be aware that the java plugin uses 
java.net for non all protocols save HTTPS.  This means that if java doesn't 
have a protocol handler for chrome, it will just fail.  This smells like an 
RFE.  I'll file it that way into sun's bug system.

N/A

What's a chrome?
  xxxxx@xxxxx   2001-08-27

For details on chrome please checkout the following URLs
http://www.mozilla.org/xpfe/ConfigChromeSpec.html
http://www.mozilla.org/docs/ora-oss2000/chatzilla/chromedirs.html

Briefly
XUL UIs are commonly referred to as ``chrome''. 

Chrome:// URLs have the following ``magic'' properties... 
          chrome://content/chatzilla resolves to
          <chrome-directory>/packages/chatzilla/chatzilla/content/chatzilla.xul 
          chrome://skin/chatzilla resolves to
          <chrome-directory>/packages/chatzilla/chatzilla/skin/chatzilla.css 
          chrome://locale/chatzilla/chatzilla.dtd resolves to
          <chrome-directory>/packages/chatzilla/ch
Chrome needs to be installed before chrome:// urls will work
  xxxxx@xxxxx   2001-10-11

Can you provide the source code for your applet?
  xxxxx@xxxxx   2001-10-12

Since no more information about this issue has been forthcoming and since this really seems to be something that would have to be handled in the Java Protocal Handlers (not the plugin).  I am closing this RFE.
  xxxxx@xxxxx   2002-02-25

This isn't just an RFE.  This is major brain damage in the
Java plugin.

I wrote my own protocol handler and while the applet no
longer gives an exception on startup java -> javascript
communciation doesn't work. 

I should note that even though you DO get this description
your applet will work fine (mine did)

http://bugzilla.mozilla.org/show_bug.cgi?id=199740