General Features

• New Directory buttons: The directory button toolbar now includes Destinations and People. Net Directory and Handbook have been removed.

• New Directory menu items: The Directory menu now has items for Netscape Destinations and People. Internet Directory and Internet White Pages have been removed.

• New Navigation for Frames and the Back button: Now, when you click on a link that updates a frame, pressing the Back button returns you to the previous state of the frame. Previously, pressing the Back button ignored updates within a page's frames and always returned you to the previous whole page (further back than you probably wanted). In short, navigating among frames now works on a per frame basis: pressing Back revisits the previous frame and pressing Forward revisits the frame ahead.

• Three-pane configurability: A pane layout option has been added to the Mail and News|Appearance panel (choose the Options|Mail and News Preferences|Appearance menu item). The panel offers radio buttons to designate the layout of the three panes in the Mail and News windows. Choose Split Horizontal (Articles on top on Macintosh) to align the message content pane to the right of the two split panes. Choose Split Vertical (Articles on left on Macintosh) to align the message content pane below the two split panes. Choose Stack (Stacked on Macintosh) to align the message content pane below the two stacked panes (layered in rows atop one another).

• Show recipient in Sent Folder and Outbox: When you select a mail folder by clicking on it, the message heading pane displays the titles of messages contained in that folder. In previous versions, you'd always see the title Sender above a column that shows the name of the sender of the mail message. Now, in the Outbox and Sent Mail folders, you'll see the title Recipient instead of Sender, and the column shows the email address of the mail recipient. For sent mail, the recipient info is much more useful than the sender info (typically yourself).

• Compressed headers: When viewing either the Mail or News window, the Options menu now offers a cascading (hierarchical) menu items called Show Headers that replaces the Show All Headers item. The new menu item gives you more options to control the number of header information fields displayed when viewing messages. All displays all possible header fields. Normal displays the primary address fields. Brief displays only subject and recipient fields.

• Netscape Navigator Gold: Netscape Navigator Gold has been updated for Win32 and Mac. Gold now lets you edit tables.

• New Network preferences panels: New Network|Protocols and Network|Languages preference panels to expand and improve user preferences for security and privacy control.

• POP3 servers: The Keep Mail on Server and Maximum Message Size options now work even with POP3 servers that do not implement the UIDL command.

• Special characters: Additional entity names such as "&pound" are now implemented.

• Frame Border Control: The FRAMEBORDER attribute can be set in the <FRAMESET> tag or the <FRAME> tag. The attribute can have the value of "yes" or "no". The default is "yes". When used in the <FRAMESET> tag this attribute sets the default value for all frames in that frameset. When used in the <FRAME> tag, it sets the presence of borders explicitly for that frame, overriding any already set frameset attributes. Because borders are shared between frames. A border will only be turned off if all the frames sharing it have their FRAMEBORDER attribute set to "no".

  The BORDER attribute can globally set the frame border thickness for all frames in a frameset tag (on the outermost <FRAMESET> only; not on a per-frame basis). Setting BORDER=>0 implicitly sets FRAMEBORDER="no".

  The BORDERCOLOR attribute sets border color in the <FRAMESET> tag or the <FRAME> tag. This attribute sets a color name or RGB value to be used as the color for frame borders. When used in the <FRAME> tag, it attempts to set the colors of that frames borders. When used in the <FRAMESET> tag, it 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.

• Multi-Column Text: The <MULTICOL> tag is a container, and all the HTML between the starting and ending tag will be displayed in a multi-column format. The tag can be nested, although multi-column text within multi-column text becomes quickly unreadable. The attributes of this tag are COLS, GUTTER, and WIDTH.

  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)
  

• Horizontal and Vertical Spacing: A new tag called <SPACER> provides better control over the spacing of objects and whitespace in HTML pages. The attributes to spacer are TYPE, SIZE, WIDTH, HEIGHT, and ALIGN.

  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 horizontal spacer inserts horizontal space between words. The width of the space is controlled by the SIZE attribute.
  • The vertical spacer inserts vertical space between lines. Implicit in this spacer is a line break to end the current line, then the vertical space is added before the beginning of the next line. The height of the space is controlled by the SIZE attribute.
  • The block spacer behaves almost exactly like an invisible image. When using this type of spacer the SIZE attribute is ignored, and instead the WIDTH, HEIGHT, and ALIGN attributes are applied just as they would be for the <IMG> tag.

  The SIZE attribute only applies when the spacer has a type of horizontal or vertical. Then this attribute controls the absolute width or height in pixels of the spacing added.

  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.

• Strikeout and Underline Text: Netscape has always supported strikeout text in the form of the <STRIKE> tag. Now Netscape also supports an alternative syntax, the <S> tag, while maintaining support for the <STRIKE> tag as backwards compatibility.

  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 in HTML: JavaScript evaluation in HTML attribute values allows JavaScript to be dynamically evaluated in the right-hand side of an HTML attribute name/value pair (that is, when calculating the values of HTML attributes). This allows the attributes of one HTML element to depend on information about previously placed elements on the page.

  JavaScript evaluation uses the HTML entity sequence as follows:

  &lt; == "<"

  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=fontName: The FONT FACE attribute lets you specify the names of specific fonts as your preferred font choices in the format:

  <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>

• Support table cell background colors: You can specify a background color to be used when displaying table cells. To specify a table background color use the bgcolor attribute. Nested tables inherit background colors.

  Color Cells

  One Color

  Another Color

  The bgcolor tag specifies one of the supported color names and can be used with the following tags: table, td, th, and tr.

  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>

Message Composition and Viewing Improvements

• Long-line Wrapping in Message Composition window: The new Message Composition window menu item View|Wrap Long Lines, when checked, automatically line-wraps the messages you send such that no line is longer than 72 characters. The width of the Message Composition window does not affect line-wrapping, nor are the line breaks you see necessarily the wrapping that is sent. When unchecked, messages are sent without automatic line-wrapping and the line breaks that you see are sent. The default is checked.

  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).

• Long-line Wrapping in Mail and News windows: The new menu item in the Mail and News windows View|Wrap Long Lines, when checked, displays long lines in the message in shorter, more numerous lines. When unchecked, long lines are more likely to extend off the screen and require the horizontal scroll bar for viewing. The default is unchecked.

  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.

The MIME message display engine has been significantly improved. A number of new features have been added and a number of bugs have been fixed.

• When saving attachments, a more reasonable default file name will be used: In earlier versions, the Save This Link As command (and its shortcut, the shift-click or option-click gesture) did not generally offer a good default file name when prompting for the place to save the attachment. This is now fixed: the suggested file name should always be the original name of the attached document.

• Support for uuencoded data in non-MIME messages is greatly improved: In previous versions of Netscape, uuencoded pseudo-attachments were not handled as well as full-fledged MIME attachments; the handling of uuencoded data in non-MIME messages should now be virtually indistinguishable from real MIME attachments, from the end user's point of view.

  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:

  • Any number of uuencoded segments in a message will be displayed as attachments: the uuencoded data is considered to extend from the begin to the end line, and then the remainder of the message will be presented in the usual way.

  • Any type of uuencoded data will be treated as an attachment, not just images. If the extension on the name of the attached file is one that indicates that it is a GIF, JPEG, or XBM, then the attachment will be decoded and displayed inline; otherwise, it will be presented as a normal attachment link, making it easy to decode and save the data to a file.

  • The View Attachments as Links menu item now affects the presentation of uuencoded attachments in the same way it has always affected MIME attachments.

  • When uuencoded attachments are saved, they will always be decoded first, just as base64-encoded data is.

• BinHex data is recognized in non-MIME messages: In much the same way that we notice the presence of uuencoded data in non-MIME messages, we now also notice BinHex data.

• Sun MailTool attachments are supported: Attachments of the form generated by Sun's MailTool (messages of type x-sun-attachment) are recognized, and displayed just like normal MIME messages.

• The multipart/alternative MIME type is supported: The multipart/alternative Content-Type is a container that includes different versions of the same document; for example, a text/plain version, followed by a text/html version, followed by an application/postscript version. Netscape will present to the user only one of the versions, the highest ``resolution'' version that can be displayed inline.

  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.)

• The message/external-body MIME type is supported: The message/external-body Content-Type is a MIME representation of what is essentially a URL: it describes a method for retrieving a document from the net. The directly-supported message/external-body access methods are ftp, anon-ftp, local-file, afs, mail-server, and url.

• Uuencoded data is only recognized in non-MIME messages: We no longer recognize uuencoded data in arbitrary parts of type text/plain: we now only do this auto-recognition in messages which have no Content-Type specified. That is, if the message is a full-fledged MIME message, we always believe the Content-Type of that message. If it says it's plain text, then we treat it as plain text and don't play guessing games behind its back.

  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.

Macintosh-only Changes

• Open Transport native: Native support for Apple Open Transport.

• Internet Config: Basic Internet Config features are supported. Internet Config is a public domain system extension that lets you configure Internet information such as email address and server names in a single source location. This is useful if you are using multiple Internet applications. Supporting applications can find this information, making it unnecessary for you to enter the same information in each of your Internet applications.

• Tooltips: An item in the Options|General Preferences|Appearance panel lets you turn on tooltips so that when the mouse stays over a toolbar button, tooltip text appears.

• Unread mail and news messages: Are now marked in bold.

• Helpers panel: The Options|General Preferences|Helpers panel has been redesigned to simplify editing, adding, and deleting helper applications and plug-ins.

• User-interface improvements: Several minor changes regarding fonts, spacing, and tabs. Improved design in toolbar and preferences panels.

• Enable active scrolling option:The General|Appearance preference panel has a check box to allow active window scrolling. When checked, movement of the scroll bar thumb causes the content area to scroll as you drag. When unchecked, movement of the scroll bar thumb causes the content area to scroll only after the mouse button is released. The default is checked. On slower computers, scrolling performance might improve when the setting is unchecked.

Windows-only Changes

• Forms Printing: The printing of forms has been improved.

• Image Presentation: Image outlines and alt text are presented before image loading.

• Set as Wallpaper: A menu item has been added to the pop-up that lets you use a specified image as the screen background image. Point the mouse cursor over any image, pres the right-mouse button, then select the Set as Wallpaper menu item.

UNIX-only Changes

• Plug-in support on UNIX platforms: SGI IRIX, SunOS, Solaris 2.3, Solaris 2.4, DEC OSF/1, HP/UX, and Linux 1.2 (ELF).

• Frame Source and Frame Info: The View menu has items for Frame Source and Frame Info, available when a frame is selected.

• Quoted text color: The Mail and News Preferences|Appearance panel has a field that lets you enter the color of your quoted text.

• Hide menu bar: The Options menu has an item to let you hide the menu bar. Use the right mouse button to display the pop-up menu containing an item to show the menu bar again.

• Drag-and-drop attachments: To create an attachment, you can drag a mail message item from the message pane to the attachment field of the Composition window.

• Drag-and-drop news: You can drag News window articles to store them in Mail window folders.

• HP/UX: The HP/UX binary has been linked dynamically.

• Helpers panel: The Options|General Preferences|Helpers panel has been redesigned to simplify editing, adding, and deleting helper applications and plug-ins.

LiveConnect

JavaScript

• JavaScript-generated documents: JavaScript-generated documents can be printed, saved as files, and viewed with View Document/Frame Source.

• Resizing a window reloads its doc from cache: Resizing a window reloads its doc from cache and had formerly rerun script tags, re-initialize global variables, and in general redo everything that JavaScript did when the page first loaded (even the onload handler was rerun). Now, no scripts are rerun, no onload is sent (nor is onunload sent), and user-defined variables and properties stay around. There is currently one exception: HTML objects (such as forms, link) can lose their user-set properties. Such objects are re-reflected by the reload caused by resizing.

• NOSCRIPT tag: A <NOSCRIPT>...</NOSCRIPT> tag has been added so that if a user has JavaScript turned off in the Network|Languages preferences panel or if a user's browser application does not support JavaScript, the user sees the HTML between the noscript tag and its end tag.

• SRC attribute: The <SCRIPT> tag now has an additional attribute that allows a JavaScript file to be specified as the JavaScript source (rather than embedding the JavaScript in the HTML). Attributes within the SCRIPT tag can now be specified as follows:

  <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.

• Data tainting security model: You can set NS_ENABLE_TAINT to enable JavaScript in one window to see properties of a second window, regardless of which server provided the second window's document. When JavaScript in the first window attempts to send to a server (other than the one that originated the data) data derived from the second window's tainted properties, a confirming dialog is brought up so that the user can cancel or confirm the transaction.

  To set NS_ENABLE_TAINT:

  • On UNIX, use setenv.
  • On Windows, use set.
  • On Macintosh, edit the resource with type 'Envi' and number 128 in the Netscape application by removing the two ascii slashes "//" before the NS_ENABLE_TAINT text at the end of the resource.
  You can use two new functions, taint() and untaint(), to mark and unmark an argument datum with taint associated with the current script. For example, to remove taint from a form input element so that it can be sent to another server by the server's script, you would say:

  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 reflection of plug-ins: Allows developers to dynamically determine what plug-ins are installed on the client. By making the list of installed plug-ins accessible through JavaScript, content developers can write simple scripts to display embedded plug-in data if the appropriate plug-in is installed, or display some alternative information (image, text, etc.) if not.

  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.

Java

• Mac Support: Java support has been added to the Macintosh Power PC and 68K platforms allowing users to run Java applets. Applets are software programs written in the Java language that can be integrated within HTML pages.

• UNIX Support: Java support has been added to the IBM AIX and BSDI platforms. The Java implementation is now compatible with version 1.0.2 of the JDK from Sun.

• Unicode Support: Java applets will now display all Unicode characters which can be rendered with an existing system font. Support is no longer limited to the Latin-1 subset of Unicode: Support is provided for Western (Latin 1) and Central European (Latin 2) languages, as well as Chinese, Japanese, and Korean. This feature is currently available on the UNIX and Macintosh platforms.

• Win 32 JIT Compiler: On Windows 32 computers, a just-in-time compiler translates Java bytecodes into Intel machine code which makes many Java programs execute substantially faster.

• Windows AWT toolkit: A completely new implementation of the AWT toolkit fixes many bugs.

• JavaScript interaction using LiveConnect: There is now a new attribute for the APPLET tag called MAYSCRIPT which is required for an applet that wishes to use LiveConnect and the netscape.javascript classes to interact with JavaScript.

Security

• New section in Security preferences panel: New Secure Network Protocol section in Security|General Preferences to control access to SSL v2 and SSL v3.

• Note: The security features described below are not yet fully implemented and do not offer any current functionality. Though elements of the user interface can be viewed in the preference panels, they should not be used. Certain buttons might cause crashes.

• Security Preferences: Two new security preference panels have been added to enable forthcoming security features. A short summary of the forthcoming features are described below.

• Personal Certificate panel: Personal certificates identify you to others on the Internet. For example, when you submit information in a form, your personal certificate allows the recipient of the form to know the information came from you and no one else.

  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.

• Passwords panel: A Netscape password protects you if your computer can be physically accessed by other people or remotely accessed through a network. Your password protects your security certificates.

International Character Encodings

• Netscape supports the following character encodings in Netscape Navigator for Web, Mail, and News: ISO 8859-1 (Latin-1), Shift-JIS, EUC-JP, JIS (ISO-2022-JP), EUC-KR, GB, Big5, EUC-TW (CNS), and ISO 8859-2 (Latin-2).

• Internally, Netscape converts these character encodings to the encodings used in the fonts on your system (which vary from platform to platform). The following is a specific list of the character encodings supported:
  • Western European: ISO 8859-1, MacRoman (Mac only)
  • East (or Central) European: ISO 8859-2, MacCE (Mac only)
  • Japanese: ShiftJIS, EUC JP, ISO-2022-JIS
  • Korean: EUC KR, ISO-2022-KR
  • Traditional Chinese: Big 5, EUC TW
  • Simplified Chinese: GB2312
  • East (or Central) European: CP 1250 (Windows Latin 2)
  • Cyrillic: ISO 8859-5, KOI8-R, MacCyrillic (Mac only), CP 1251 (Windows Cyrillic)
  • Greek: ISO 8859-7, MacGreek (Mac only)
  • Turkish: ISO 8859-9, MacTurkish (Mac only)

LiveAudio

• Plug-in: This plug-in is an asynchronous sound-playing application, capable of playing AIFF, MIDI, WAV, and AU sound formats. The plug-in can be controlled using various views.

• Supported Platforms: Win 16, Win 32, Mac 68K, and Mac PPC

• System Requirements:
  • Win 16: (Minimum) 386 Processor with Windows 3.1, and a compatible sound card installed.

  • Win 32: (Minimum) 386 Processor with Windows 95 or Windows NT, and a compatible sound card installed.

  • Macintosh (68K): (Minimum) Macintosh 68030, with System 7.1, QuickTime 2.1 (with Musical Instrument Plug-in), and Sound Manager 3.1.

  • Macintosh (PPC): (Minimum) Macintosh with a PPC 601 (66MHz), System 7.1.2, QuickTime 2.1 (with Musical Instrument Plug-in), and Sound Manager 3.1.

Live3D

• Plug-in: This plug-in extends Netscape Navigator so that you can experience distributed, interactive 3D spaces rich with text, images, animation, sound, music, and video. In addition to providing a high-performance VRML viewer, Live3D extends Netscape's Java, JavaScript, and plug-in interfaces to make it easy to develop distributed 3D applications on the Netscape Navigator platform.

• Supported Platforms: Win 32, Win 16, Macintosh PPC

• System Requirements:
  • PC (Windows 95, Windows NT, or Windows 3.1): Live3D for Windows requires that you have a Pentium or a 486DX CPU, or a 486SX CPU with a math co-processor, 8mb of RAM, 2.5mb of disk space, and at least a 256 color display.

  • Macintosh (PPC): System 7.x

LiveVideo

• Plug-in: This plug-in will play AVI movies. AVI is a common video format on Windows.

• Supported Platforms: Win 16, Win 32

• System Requirements:
  • Win 16: (Minimum) 386 Processor with Windows 3.1, and a compatible sound card installed. Will require "Video for Windows."

  • Win 32: (Minimum) 386 Processor with Windows 95 or Windows NT, and a compatible sound card installed.

QuickTime

• Plug-in: This plug-in automatically plays QuickTime movies (.mov files) including movies with text, MIDI, and other kinds of data. A page developer can use HTML commands to automatically play a movie for you or to present a controller giving you the ability to play, stop, fast-forward, and rewind movies.

• Supported Platforms: Win 16, Win 32, Mac 68K, and Mac PPC

• System Requirements:
  • PC (Win 16 or Win 32): Windows 95, NT, or 3.1, compatible sound card, and QuickTime 2.1.1 for Windows.

  • Macintosh (68K or PPC): Macintosh with System 7.0 or later, QuickTime 2.1, and Sound Manager 3.2.

CoolTalk

• Installing under Windows NT 4.0: If you run the installer and nothing happens, try restarting Windows and running the installer again.

• Configuring Live3D for 16 bit Windows: Move the 3DNS16A.EXE file from your plugins directory to a temporary directory. Double click on the file to launch the Live3D installer.

• In 16 bit Windows version, both CoolTalk and AVI Plugins requires Video for Windows.