The Next Big Thing?

Some of these are more important then others.

• line #4: unknown attribute "TOPMARGIN" for element (BODY).
  
• line #4: unknown attribute "LEFTMARGIN" for element BODY.
  
• line #4: BODY must immediately follow /HEAD|NOFRAMES|/FRAMESET
  
• line #4: BODY but no HEAD.
  
• line #6: illegal value for BGCOLOR attribute of TD (FFFFFF)
  
• line #6: unknown attribute "BACKGROUND" for element TD.
  
• line #38: attribute BORDER is repeated in element TABLE
  
• line #40: unknown attribute "TOPMARGIN" for element BODY.
  
• line #40: unknown attribute "MARGINHEIGHT" for element BODY.
  
• line #40: unknown attribute "LEFTMARGIN" for element BODY.
  
• line #40: unknown attribute "MARGINWIDTH" for element BODY.
  
• line #40: illegal value for BGCOLOR attribute of BODY (FFFFFF)
  
• line #40: illegal value for LINK attribute of BODY (0000FF)
  
• line #40: illegal value for ALINK attribute of BODY (000066)
  
• line #40: illegal value for VLINK attribute of BODY (0000FF)
  
• line #40: BODY must immediately follow /HEAD|NOFRAMES|/FRAMESET
  
• line #40: tag BODY should only appear once. I saw one on line 4!
  
• line #40: BODY but no HEAD.
  
• line #40: should set all or none of BGCOLOR, TEXT, LINK, ALINK, VLINK attributes on BODY element
  
• line #51: empty container element FONT.
  
• line #60: /CENTER on line 60 seems to overlap B, opened on line 57.
  
• line #63: setting WIDTH and HEIGHT attributes on IMG tag can improve rendering performance on some browsers.
  
• line #71: markup embedded in a comment can confuse some browsers.
  
• line #182: value for attribute color (#ff0000) of element FONT should be quoted (i.e. color="#ff0000")
  
• line #191: value for attribute color (#ff0000) of element FONT should be quoted (i.e. color="#ff0000")
  
• line #239: value for attribute color (#ff0000) of element FONT should be quoted (i.e. color="#ff0000")
  
• line #265: leading whitespace in content of container element LI
  
• line #267: leading whitespace in content of container element LI
  
• line #269: leading whitespace in content of container element LI
  
• line #274: /CENTER on line 273 seems to overlap B, opened on line 273.
  
• line #286: value for attribute color (#ff0000) of element FONT should be quoted (i.e. color="#ff0000")
  
• line #306: leading whitespace in content of container element LI
  
• line #307: leading whitespace in content of container element LI
  
• line #308: leading whitespace in content of container element LI
  
• line #309: leading whitespace in content of container element LI
  
• line #310: leading whitespace in content of container element LI
  
• line #311: leading whitespace in content of container element LI
  
• line #312: leading whitespace in content of container element LI
  
• line #313: leading whitespace in content of container element LI
  
• line #314: leading whitespace in content of container element LI
  
• line #315: leading whitespace in content of container element LI
  
• line #316: leading whitespace in content of container element LI
  
• line #317: leading whitespace in content of container element LI
  
• line #318: leading whitespace in content of container element LI
  
• line #319: unmatched /OL (no matching OL seen).
  
• line #321: illegal context, UL, for text; should be in LI or LH.
  
• line #350: value for attribute color (#000000) of element FONT should be quoted (i.e. color="#000000")
  
• line #358: setting WIDTH and HEIGHT attributes on IMG tag can improve rendering performance on some browsers.
  
• line #363: /B on line 351 seems to overlap CENTER, opened on line 362.
  
• line #409: value for attribute color (#0000ff) of element FONT should be quoted (i.e. color="#0000ff")
  
• line #571: no closing /TABLE seen for TABLE on line 403.
  
• line #571: no closing /FONT seen for FONT on line 350.
  
• line #571: no closing /FONT seen for FONT on line 328.
  
• line #571: no closing /UL seen for UL on line 304.
  
• line #571: no closing /FONT seen for FONT on line 298.
  
• line #571: no closing /FONT seen for FONT on line 286.
  
• line #571: no closing /B seen for B on line 286.
  
• line #571: no closing /TABLE seen for TABLE on line 282.
  
• line #571: no closing /FONT seen for FONT on line 251.
  
• line #571: no closing /FONT seen for FONT on line 239.
  
• line #571: no closing /B seen for B on line 239.
  
• line #571: no closing /TABLE seen for TABLE on line 235.
  
• line #571: no closing /FONT seen for FONT on line 204.
  
• line #571: no closing /TABLE seen for TABLE on line 197.
  
• line #571: no closing /FONT seen for FONT on line 195.
  
• line #571: no closing /FONT seen for FONT on line 191.
  
• line #571: no closing /FONT seen for FONT on line 186.
  
• line #571: no closing /FONT seen for FONT on line 72.
  
• line #572: no closing /TABLE seen for TABLE on line 38.
  
• line #572: no closing /CENTER seen for CENTER on line 38.
  
• line #572: no closing /TABLE seen for TABLE on line 5.
  
• line #572: no closing /BODY seen for BODY on line 4.

For example line #4: unknown attributes "TOPMARGIN" and LEFTMARGIN" for the BODY element are browser specific tags, and although a validator may reject them, there is nothing wrong with leaving these tags in place. Validators usually conform to the W3C guidelines -- unfortunately the companies who make the browsers do not always comply.

Boyd must be using Netscape 4.x because using a GECKO based browser (K-Meleon, based on Gecko (the mozilla rendering engine) that powers Mozilla and Netscape 6.x) the page displays fine.

The BIG problems for Netscape 4.x browsers will be the document structure such as BODY elements with missing HEAD elements, and the closing TABLE tags, which are a BIG "no-no" for Netscape 4.x.

Overlaying FONT tags in the midst of other tags in multiple instances can also cause an eventual break down in Netscape 4.x because each browser only has a limited amount of error correction it can perform. Font tags have been deprecated which means it is one that has been outdated by newer constructs and a style sheet should be used to describe font properties. Netscape supports most of CSS1 and some of CSS2 but you can cascade style sheets with one displaying selectors, properties and values supported by Netscape 4.x and @import another one for browsers that have a better grasp of CSS2 properties. To get a better idea how to do this you might want to read my article Different Stylesheets for Different Browsers

Hope this helps!

Best Regards,
Steve MacLellan




homebusiness-websites.com

Hi,

I meant to thank you for telling us about Crazy Browser. I use it all the time.

I use Netscape 4.7 for my surfing where I want to sweep up my tracks afterward. For that I use NS Washer, and I even use Scorch to overwrite my swap file every time I restart.

(I'm considering using a method where I can surf without being monitored by sites or by my ISP or by the Atty General, I'm really getting concerned about privacy issues and America is a strange country in certain ways.)

I also use Netscape as a sort of initial page checker (I check all my pages with Doctor HTML which I believe I also heard about from you).

Best,

- Boyd

Hi Boyd,

You may know about this already, but in case you don't....

Windows keeps a record of your web browsing history - even AFTER you've cleared your history and cache with Internet Explorer....

The article (below) explains this, and also tells you what you can do about it.

(Be warned - there is strong language in the web site name, which some might find offensive.)

- Dien Rice


Microsoft's hidden files....

dno
> Hi Boyd,

> You may know about this already, but in case
> you don't....

> Windows keeps a record of your web browsing
> history - even AFTER you've cleared your
> history and cache with Internet Explorer....

> The article (below) explains this, and also
> tells you what you can do about it.

> (Be warned - there is strong language in the
> web site name, which some might find
> offensive.)

> - Dien Rice