First impression on unpacking the Q702 test unit was the solid feel and clean, minimalist styling.
Troubleshooting in HTML
- — 01 February, 2002 11:43
An important part of coding is error checking. This month, we examine browser-related problems and also introduce HTML Validator Lite, which is a troubleshooting program that can identify syntax errors.
NETSCAPE VS INTERNET EXPLORER
You may have noticed inconsistencies in the way different browsers interpret Web pages. We'll focus on the two most popular, Internet Explorer (IE) and Netscape (NS). Other browsers may encounter similar problems, but, in most cases, consideration of the issues that follow should eliminate comparable errors across the board.
When creating a Web site, you must identify your testing parameters: whether to test the site at one or both popular screen resolutions (800x600 or 1024x768); whether to test the site with various text sizes (for IE go to View-Text size; for NS go to View-Increase Font); and, most importantly, which browsers and browser versions to accommodate.
When considering these points, the determining factor should not be which settings you personally prefer, rather, it should be which settings the majority of your viewers use. Some people code their sites specifically for IE, or only for Netscape. This is fine, as long as you realise that a significant percentage of the Internet population may consequently view the site in a less than perfect state.
Let's assume the decision is to code your site for both NS and IE (generally accommodating browser versions 4.x upwards).
Closing tags. By and large, when IE encounters a tag that is not closed off it will do it itself. Netscape, on the other hand, is not so forgiving, and leaves the tag open. View the following code in both IE and NS and notice the difference created by an absence of </TABLE>.
<TD> one </TD>
<TD> two </TD>
Background colours and graphics in tables. Limit your use of background graphics and colours in tables, especially when using cellspacing as NS re-starts the graphic for each TD, and omits the background for cellspacing. IE, though, continues the picture across the table. Click here to see an example of this situation.
File name conventions. A good rule of thumb is to not use spaces in file names, whether they are graphic or HTML files; Netscape has been known to get confused. Take the following, for example:
<IMG src="my dog.gif" alt="puppy dog">
Netscape could see this and try to find a file called 'my', interpreting the space as an indication that it has reached the end of the value name. Consequently, the graphic may not display. This problem is not consistent, but it's best to replace the spaces in file names with underscores - my_dog.gif - or, alternatively, omit the space altogether, as in mydog.gif.
HTML VALIDATOR LITE
This freeware program greatly assists you with troubleshooting, and you can find it at http://www.htmlvalidator.com/lite/. When using this software, the first thing to do is close off any other editing instances of the file. Otherwise, you may save changes in Validator, go back to your open Notepad file, save it, and thereby accidentally save over any changes you made in Validator.
Click the red 'H' to calculate the errors. You will see three windows - the top is your code (which you may edit here); the bottom two are descriptions of the specific errors. The left is a list of all errors, the right is an easier-to-read description of the selected mistake.
When you highlight an error (bottom left window), the cursor is taken to the specific place in the file.
It is a good idea to fix errors in the order that they appear, as they may have a cumulative affect. For example, <img src="dog.gif> would cause many errors because of the lack of a closing quote. As soon as this error is fixed, however, most of the other problems vanish.