HTML Tags for Java Applets, circa 1999
In 1999, I took a class in Java at Santa Monica College. I was interested at the time in the small variations among how The W3C, Sun, Netscape, and Microsoft specified the <APPLET> tag.
So here are how each specified the tag in 1999, minus the formatting of the original pages:
W3C - HTML 3.2 | W3C - HTML 4.0 | Microsoft | Netscape | Sun
https://www.w3.org/TR/REC-html32.html#applet APPLET (Java Applets) <!ELEMENT APPLET - - (PARAM | %text)*> <!ATTLIST APPLET codebase %URL #IMPLIED -- code base -- code CDATA #REQUIRED -- class file -- alt CDATA #IMPLIED -- for display in place of applet -- name CDATA #IMPLIED -- applet name -- width %Pixels #REQUIRED -- suggested width in pixels -- height %Pixels #REQUIRED -- suggested height in pixels -- align %IAlign #IMPLIED -- vertical or horizontal alignment -- hspace %Pixels #IMPLIED -- suggested horizontal gutter -- vspace %Pixels #IMPLIED -- suggested vertical gutter -- > <!ELEMENT PARAM - O EMPTY> <!ATTLIST PARAM name NMTOKEN #REQUIRED -- The name of the parameter -- value CDATA #IMPLIED -- The value of the parameter -- > Requires start and end tags. This element is supported by all Java enabled browsers. It allows you to embed a Java applet into HTML documents. APPLET uses associated PARAM elements to pass parameters to the applet. Following the PARAM elements, the content of APPLET elements should be used to provide an alternative to the applet for user agents that don't support Java. It is restricted to text-level markup as defined by the %text entity in the DTD. Java-compatible browsers ignore this extra HTML code. You can use it to show a snapshot of the applet running, with text explaining what the applet does. Other possibilities for this area are a link to a page that is more useful for the Java-ignorant browser, or text that taunts the user for not having a Java-compatible browser. Here is a simple example of a Java applet: <applet code="Bubbles.class" width=500 height=500> Java applet that draws animated bubbles. </applet> Here is another one using a PARAM element: <applet code="AudioItem" width=15 height=15> <param name=snd value="Hello.au|Welcome.au"> Java applet that plays a welcoming sound. </applet> codebase = codebaseURL This optional attribute specifies the base URL of the applet -- the directory or folder that contains the applet's code. If this attribute is not specified, then the document's URL is used. code = appletFile This required attribute gives the name of the file that contains the applet's compiled Applet subclass. This file is relative to the base URL of the applet. It cannot be absolute. alt = alternateText This optional attribute specifies any text that should be displayed if the browser understands the APPLET tag but can't run Java applets. name = appletInstanceName This optional attribute specifies a name for the applet instance, which makes it possible for applets on the same page to find (and communicate with) each other. width = pixels height = pixels These required attributes give the initial width and height (in pixels) of the applet display area, not counting any windows or dialogs that the applet brings up. align = alignment This attribute specifies the alignment of the applet. This attribute is defined in exactly the same way as the IMG element. The permitted values are: top, middle, bottom, left and right. The default is bottom. vspace = pixels hspace = pixels These optional attributes specify the number of pixels above and below the applet (VSPACE) and on each side of the applet (HSPACE). They're treated the same way as the IMG element's VSPACE and HSPACE attributes. The PARAM element is used to pass named parameters to applet: <PARAM NAME = appletParameter VALUE = value> PARAM elements are the only way to specify applet-specific parameters. Applets read user-specified values for parameters with the getParameter() method. name = applet parameter name value = parameter value SGML character entities such as é and ¹ are expanded before the parameter value is passed to the applet. To include an & character use &. Note: PARAM elements should be placed at the start of the content for the APPLET element. This is not specified as part of the DTD due to technicalities with SGML mixed content models.