When I choose the Preview in Browser command, the following message appears: "Sorry, not enough memory to open the browser application. Try quitting some other applications."
There is not enough memory to open the browser application at the same time as Claris Home Page.
On a PC with Windows, some browsers will restart each time a page is previewed and a new copy of the application is opened. To free memory, close the application windows not in use.
On the Macintosh, try reducing the amount of memory allocated to the browser (by selecting the browser's icon in the Finder operating system software and choosing Get Info from the File menu), or follow the usual steps for making more memory available: quitting other applications, turning off extensions, etc. Typically, you will need a Macintosh equipped with at least 12 megabytes of memory to run Claris Home Page and a browser application at the same time.
When I choose the Preview in Browser command, the browser opens, but the file is not displayed.
The browser may not be installed correctly. Some browsers (notably, Internet Explorer for Windows) can be damaged by applications that change registry entries, causing the system to incorrectly send "open file" messages to them. Re-install a fresh copy of the browser if you have this problem.
When I choose the Preview in Browser command, some other error message appears, such as "Sorry, an error occurred (-xx) while attempting to open the browser application", or "Sorry, an error occurred while attempting to send this file to the browser."
There may be a problem with the browser application you have selected as the default, or the browser application may be missing.
Choose Application Options from the Tools menu (Windows) or Preferences from the Edit menu (Macintosh) to open the Preferences dialog box. Click the Browser Preview tab to display a new set of options. Click Clear and re-select the browser.
My page doesn't look quite the same in the browser as it does in Claris Home Page (different fonts, lines are broken at different positions, etc.).
The HTML standard does not precisely define the appearance of a document. It sets broad guidelines, but individual programs (such as browsers) are free to use their own variations. Therefore, it is impossible to create an HTML file that will look exactly the same in every browser.
Claris Home Page 3.0 attempts to display HTML documents as they will appear in Netscape Navigator 2.0 (based on Navigator's default preferences settings). Certain features (such as table layout) are implemented differently in Claris Home Page than in Navigator, and minor differences in spacing are inevitable. With other browsers, or if you have altered Navigator's font preferences, there will be greater differences. Finally, your document may use advanced features not supported by other browsers, such as tables, frames, or colored text.
If you plan to publish your HTML document on the Internet, it may be viewed by many different browsers on many different platforms. Therefore, you should not attempt to, or expect to, precisely control the layout and appearance of your document. Even if your HTML document is to be used locally (on an "Intranet"), users may employ different browsers or have customized font preferences and other browser settings that will affect the appearance of the document.
When I view my page in a browser, a strange character sometimes appears on blank lines.
Claris Home Page inserts a non-breaking space character (represented by the ISO Latin Character code, ) on what are otherwise blank lines. This is done to work around the interpretation of HTML by certain browsers, such as Netscape Navigator, which ignores blank lines. Unfortunately, other browsers sometimes incorrectly interpret this HTML as representing a different (non-blank) character: for example, Netscape Navigator 2.0 with "Japanese encoding autodetect" enabled sometimes does this.
Links within my Web site work fine in Preview Page mode, but don't work when I click on them in a browser.
A variety of problems can cause links to function incorrectly (see Problems with links). One additional problem that can occur outside of Claris Home Page involves the Base Document URL text box in the Document Options dialog box. Claris Home Page 3.0 assumes that this field (which corresponds to the <BASE> tag in the HTML source), if not empty, contains the URL of the document in which it appears. If you enter a different URL in this text box, relative links may not work correctly. The solution is to remove the value in the Base Document URL text box, or set it to the URL of the page in question, and then use the Link Editor to re-create any malfunctioning links in that page.
Images from the Claris Home Page libraries work fine when I view my pages on my local computer, but don't work when I upload my site to a Web (HTTP) server.
When uploading your site to a Web server, you need to make sure to include all files used in the site, including image files. The standard way to do this is to create an Images folder inside the folder that contains your site, and to place all image files in this folder. When you transfer (upload) the site folder to a server, the images will automatically be included.
When you insert an image from a library into your document, Claris Home Page uses the path to the original image file in the Content folder. To correct the problem, you need to copy the actual image file into your site's Images folder, and replace all references in your site to the original image file with references to the new file or open the Site Editor and use the consolidate feature.