These release notes cover:
The FRAMEBORDER attribute determines how frame borders are displayed (outline-3D or plain). The attribute can be set with the value FRAMEBORDER=YES (outline-3D border) or FRAMEBORDER=NO (plain border), and can be used in the <FRAMESET> tag or the <FRAME> tag. The default is FRAMEBORDER=YES. When used in the <FRAMESET> tag, the FRAMEBORDER attribute sets the default value for all frames in the frameset. When used in the <FRAME> tag, the attribute applies only to the particular frame, overriding any frameset attribute. Because borders are shared between frames, a border will be plain only if all adjacent frames have their attribute set FRAMEBORDER=NO.
The BORDER attribute determines the thickness of frame borders for all frames in a frameset tag. The attribute can be set with a value from 0 to N, and can only be used on the outermost <FRAMESET> (not on a per-frame basis). For example, setting BORDER=0 positions adjacent frames with no border space between them, BORDER=3 positions adjacent frames with 3 pixels of border space between them, and so on. The default is BORDER=5.
Remember, when neither a FRAMEBORDER or BORDER attribute is specified, the default is an outline-3D frame with a width of 5. Setting FRAMEBORDER=NO without a BORDER attribute displays a plain border with a width of 5. Unless you explicitly specify BORDER=0, a frame border is displayed.
Note also that when FRAMEBORDER=YES and BORDER is used, the thicker, outline borders acquire a 3-D appearance.
The BORDERCOLOR attribute determines the color of frame borders. The attribute can be set with a color name or RGB value, and can be used in the <FRAMESET> tag or the <FRAME> tag. When used in the <FRAME> tag, the attribute attempts to set the colors of the frame's borders. When used in the <FRAMESET> tag, the attribute attempts to set the colors of all borders of all frames in the frameset.
Because frame borders are shared, border color conflicts are resolved as follows: The attribute appearing in the outer <FRAMESET> has the lowest priority. This is, in turn, overridden by the attribute used in a nested <FRAMESET> tag. Finally, the BORDERCOLOR attribute used in a <FRAME> tag overrides all previous <FRAMESET> tag uses. If there is a conflict for two colors of equal priority both set on the same edge, the behavior is undefined.
The COLS attribute is mandatory and controls how many columns the display will be split into. Layout will attempt to flow elements evenly across the columns to make each column have about the same height. Unless the WIDTH attribute is specified, column with is adjusted to fill the available view.
The GUTTER attribute controls the pixels of space between columns. It defaults to a value of 10.
The WIDTH attribute controls the width of an individual column. All
columns are always the same width, so the overall width of a multi-column
layout is:
(cols * width) + ((cols - 1) * gutter)
The TYPE attribute has three possible values: horizontal, vertical, and block. These correspond to the three types of spacing control delineated above. The default value is horizontal.
The WIDTH attribute only applies when the spacer is of type block. Then this attribute controls the absolute width in pixels of the spacing rectangle added.
The HEIGHT attribute only applies when the spacer is of type block. Then this attribute controls the absolute height in pixels of the spacing rectangle added.
The ALIGN attribute only applies when the spacer is of type block. Then this attribute controls the alignment of the spacing rectangle in exactly the same way it would control the alignment of an <IMG> tag.
Netscape now supports underlined text using the <U> tag. The tag causes all text between the start and end tag to have a solid underline drawn along the common baseline of the text.
JavaScript evaluation uses the HTML entity sequence as follows:
< == "<"
Where "&" denotes the start of an entity, and ";" terminates it. In this case a dynamic entity is in the form of a JavaScript expression enclosed in curly braces:
&{javascript_expression}; == "returned_string"
JavaScript entities concatenate with the surrounding text:
"&{10 * 10};%" == "100%"
JavaScript entities can only be interpreted on the right-hand side of HTML attribute name/value pairs.
<FONT FACE="font1,font2,fontN"> </FONT>
For example, if font1 is not available, font2 is used. If no specified font is available, the default font is used. COLOR and SIZE attributes can be specified along with the FACE attribute.
<FONT FACE="Garamond,Helvetica,Times"> </FONT>
| One Color |
| Another Color |
Here's the HTML that produced the table on the right.
<TABLE ALIGN=RIGHT BORDER=1 WIDTH=20%> <CAPTION CENTER Valign=BOTTOM>Color Cells</CAPTION> <TR><TD BGCOLOR=#ffdddd>One Color</TD></TR> <TR><TD BGCOLOR=#ccffff>Another Color</TD></TR> </TABLE>
In previous versions, long lines were wrapped at the width of the window. This gave a "What You See Is What You Get" aspect to the message composition window. Regardless of whether the sender had allowed text to auto-wrap, or had hit return at the end of every line, or had resized the window, the recipient of the message would see the same line breaks as the sender.
However, problems occurred when senders made their composition windows very wide for ease of editing. It was very easy to accidentally send out messages with long lines that exceeded the 80 column limit. To many recipients, such messages would be very difficult to read.
In this version, outgoing text is wrapped at 72 columns, regardless of the size of the window. This makes the composition window less WYSIWYG, but it does make it much harder to accidentally generate unreadable messages.
There is (and has been) a single exception to the line wrapping rule: Lines which have the character > as their first character are never wrapped. Such lines are usually a part of quoted text and it is important to preserve the special character at the start of each line.
It is also still true that lines beginning with > will appear to be wrapped in the Message Composition window if the lines are longer than the window is wide. This is a property of the platform-provided text editors. At the time the message is sent, these lines will be effectively unwrapped.
Since the column at which word-wrapping occurs is no longer tied to the size of the window, the Wrap Long Lines option has been added to turn off word-wrapping on the Message Composition window. This is for the less common case where you need to send a message with specially-formatted text such as wide tables or charts, or data where wrapping the lines would damage the data.
When this option is selected, two things happen: First, the text area no longer does word-wrapping (a horizontal scrollbar will be presented instead). Second, the generated message will have exactly the line breaks that the user inserted explicitly and no automatic wrapping of any kind will occur.
The default for the option is to wrap lines and the option is not persistent. If you turn wrapping off, the particular composition window is affected only this one time (since no-wrapping is an unusual case).
Messages marked as text/plain should have preformatted line breaks so that the text does not require reformatting or wrapping. However, two forms of messages cause problems:
First, there are the messages which have line breaks at the end of each line, but which have lines which are too long (say, 100 character lines rather than 79 character lines.) Such messages were easy to generate with earlier versions of Netscape by simply making the Message Composition window wider than its default size.
Second, there are the messages which only have line breaks at the end of each paragraph. These messages are generated by software which does not understand the requirements of Internet mail and inappropriately assumes that the recipient of the message will always be able to rewrap the messages.
To address both types of message, the Wrap Long Lines option has been added to the View menu on both the Mail and News windows. This allows lines which are longer than the width of the window to be wrapped. Turning this option on will probably make correctly-formatted messages look worse, however, for messages which are incorrectly formatted with overly long lines, the option makes the messages readable.
Note that though there are now line-wrapping options on both the Message Composition window, and on the Mail and News windows, they do very different things. The former affects the actual text that will be mailed out; the latter merely controls the presentation of received messages without actually altering them.
In previous versions, uuencoded data was automatically decoded only if it appeared to be on of the built-in image types (GIF, JPEG, and XBM); and once the uuencoded data was encountered, it was considered to extend from the begin line to the end of the message. This has been fixed:
Netscape does not currently have the ability to generate messages which contain multipart/alternative data, but it is now capable of displaying it (for compatibility with existing and future mailers which do generate such messages.)
However, if the message does not have a Content-Type, then it is not a MIME message, and we assume that it may contain either text, or uuencoded data, or BinHex data, or any combination thereof.
So if you come across a message that contains uuencoded data, and we did not present it as an attachment, then that's probably because that message was generated by simply pasting the uuencoded data into the main body of the message with a MIME-compliant mailer.
The proper way to send uuencoded data with a MIME-compliant mailer is to attach the uuencoded file to the message, so that it shows up as a MIME part, with some non-text Content-Type, and x-uuencode as its Content-Transfer-Encoding.
wysiwyg://(id)/
where (id) after the literal 'wysiwyg://' and before the third '/' is automatically generated.
<SCRIPT LANGUAGE=JavaScript SRC=mySource.js>
where mySource.js is the URL (relative or full address) of the JavaScript source code file.
The LANGUAGE attribute is mandatory unless the SRC attribute is present and specifies the scripting language. The SRC attribute is optional and, if given, specifies a URL that loads the text of a script. Both attributes may be present.
The SRC attribute specifies the scripting language by using the .js suffix. The suffix must be mapped by the web server to the MIME type "application/x-javascript" which the server sends back in the HTTP GET reply's Content-type: header. Without a properly configured server (one that maps .js filename suffix to application/x-javascript MIME), Netscape won't respond properly with the data coming back in the HTTP response to the SRC-initiated request.
To set NS_ENABLE_TAINT:
untainted = untaint(document.form1.input3)
// now untainted can be sent in a URL or form post by other scripts
Neither taint() nor untaint() modifies its single argument. Rather, both functions return a marked or unmarked reference to the argument object, or a copy of the primitive type value (number or boolean value).
JavaScript currently has a global "navigator" object which contains properties for information not associated with any particular document. This object now has two additional properties: a "mimeTypes" object and a "plugins" object.
The mimeTypes object is an array of all MIME types supported by the client (either internally, via helper apps, or by plug-ins). Each element of the array is a mimeType object, which has properties for its type, description, and file extensions.
The plugins object is an array of all plug-ins currently installed on the client. Each element of the array is a plugin object, which has properties for its name and description, as well as a subarray of mimetype objects for the types supported by that plugin.
<applet archive="Nuclear.zip" code="NuclearPlant.class" width=680 height=473> </applet> This will cause the file Nuclear.zip to be downloaded to the user's disk, and will search it for the NuclearPlant class and the classes it requires. The zip file is found relative to the codebase path, and must not be compressed. Classes not in the zip file will still be searched for via the old mechanism if required.
You may wish to obtain more than one personal certificate. Some web sites may request (and issue to you) a personal certificate for specific use with their site. You may also obtain more generic personal certificates that represent you for credit card transactions or other nonspecific, secure communications.
wdog.exe /v "path to CoolTalk executable"\cooltalk.exe
<A HREF="mailto:user%25uucp-host@somewhere.com">mail</A> to send mail to: user%uucp-host@somewhere.com
http://sample-cgi/program.pl?topic=man§ion=allis turned into
http://sample-cgi/program.pl?topic=man§ion=all
