<basefont size=2>
Basefont is size 2, <b>bold</b> <i>italic</i> <tt>tt</tt><br>
<basefont size=3>
Basefont is size 3, <b>bold</b> <i>italic</i> <tt>tt</tt>
<BR>
<BR clear="left">
<BR clear="right">
<center>
</center>
<HR size=1>
<HR size=20>
<HR width=30>
<HR width=30%>
<HR width=50% align="left">
<HR width=50% align="centre">
<HR width=50% align="right">
<HR size=5 noshade>
<ISINDEX prompt="What?">
Use the extensions to <OL> and <UL> in preference to the extensions to <LI>.
<ol type=1>
- <li>
- <li><ol type=a>
- <li>
- <li><ol type=i>
- <li>
- <li><ol type=A>
- <li>
- <li><ol type=I>
- <li>I could go on
</ol>
</ol>
</ol>
</ol>
</ol>
<ol start=5>
- <li>
- <li><ol start=9>
- <li>
- <li>
- <li>And so on
</ol>
</ol>
<NOBR>
</NOBR>
<ul type=disc>
- <li><ul type=circle>
- <li><ul type=square>
- <li>I could go on
</ul>
</ul>
</ul>
The text might contain long strings like
this-is-a-long-string-with-lots-of-hyphens-in-it which just cant be broken
very easily without screwing up the page appearance
Examples
I'm afraid the explanation is too esoteric for me to simplify (or understand)
So you're going to have to look at the original netscape documentation
for this
With the release of Java, The push pull mechanism of netscape
will have to be dismissed into the domains of the obsolete.
Captions align to the top by default.
This mechanism could also be used to mail a file.
by adding WBRs the problem is solved.
this-
character codes
In addition to the usual
& escaped entities:
® -> Registered Trademark -> ®
© -> Copyright -> ©
backgrounds
<BODY [BACKGROUND=image]
[BGCOLOR=#rrggbb]
[TEXT=#rrggbb]
[LINK=#rrggbb]
[VLINK=#rrggbb]
[ALINK=#rrggbb] >
Document here
</BODY>
dynamic documents and the art of pushing and pulling
<sub> ... </sub>
Subscripts, Ideal for really <sub>tiny</sub> text.
<sup> ... </sup>
Superscripts, Ideal for really
<sup>tiny</sup> text. in a different position to
subscripts 1
<small> ... </small>
Uses a <small>smaller</small> font if available.
tables
<TABLE [border=size] [cellpadding=value] [cellspacing=value] [colour information]>...</TABLE>
<TR [rowspan] [align=alignment] [valign=alignment]>..</TR>
<TD [nowrap] [align=alignment] [valign=alignment]>..</TD>
<TH [nowrap] [align=alignment] [valign=alignment]>..</TH>
<CAPTION [align=alignment]>..</CAPTION>
<MAP NAME="map_name">...</MAP>
This defines a client side image map.
The default url is normally set to be the current document.
THe behaviour of the browser when overlapping areas are defined is not
documented.
<MAP NAME=name >
<!-- DEFAULT HREF="default_url" -->
<AREA SHAPE="RECT" HREF="url1" COORDS="x1,y1,x2,y2" TARGET="frame_name">
<AREA SHAPE="CIRCLE" HREF="url2" COORDS="origin_x,origin_y,x2,y2" TARGET="frame_name">
<AREA SHAPE="POLY" HREF="url3" COORDS="x1,y1,x2,y2,..." TARGET="frame_name">
</MAP>
<IMG SRC="url" USEMAP="#name">
<P align=[left,right,center]>...</P>
<DIV align=[left,right,center]>...</DIV>
<P align=left>
the default behaviour of your browser is for the text
to line up with the left hand edge of the page.
</P>
<P align=right>
But it can
be
aligned to the
right hand side.
</P>
<P align=center>
Or to the center
just like the <center> tag
</P>
uploading data using <INPUT type="file">
Filling forms can be tedious, sometimes more detailed information is needed.
This is possible using:
<FORM ENCTYPE="multipart/form-data" ACTION=URL METHOD=POST>
<input name=variable_name type="file">
</FORM>
The file will be sent to the server and it is the responsibility of the script
that gets it to decipher the contents of file contained in variable_name
<Marquee>text to scroll</Marquee>