The Pistoleer wrote:
I have an inconsistent problem with some Internet pages when using Netscape
(7.1) that I cannot reproduce with IE nor locally. Below is an example
link.
There are several tables on the pages. The tables at the top containing
small images are working correctly. The tables below that contain product
descriptions and input to purchase an item, these table have a problem with
Netscape. Sometimes one or more of these tables will just display the
headers, only with Netscape served from the Internet but not served from my
local test machine nor with IE. What might be causing this?
Example problem page: http://www.pistoleer.com/targets/rifle/
Pete
Your page has 566 validation errors (link broken to avoid scrolling):
http://validator.w3.org/check?uri=ht....pistoleer.com
%2Ftargets%2Frifle%2F&charset=%28detect+automatica lly%29&doctype=Inline&verbose=1
You should quote all of your attribute values to avoid errors.
"Why attribute values should always be quoted in HTML"
http://www.cs.tut.fi/~jkorpela/qattr.html
"By default, SGML requires that all attribute values be delimited using
either double quotation marks (...)"
http://www.w3.org/TR/html4/intro/sgm...tml#attributes
You have 1 table with this code:
<P><TABLE WIDTH=100%>
Now, a table can not nested inside a <p> and width=100% will be treated
as width of 100 pixels, not 100% of the available width of its parent.
I would remove all of the onmouseover spamming in the status bar: most
browsers nowadays neutralize such spamming and you'll unneedlessly annoy
the others who do not use proxomitron.
By removing all these onmouseover and onmouseout attributes, you also
reduce the tag soup.
Excessive force put on the status bar also scares potential customers.
You see, status bar is the standard browser chrome by which a browser
[should] communicate genuine unaltered information and notification
about Secure Socket Layer, encryption power, padlock icon open/closed,
cookie icon, http connection, requests, ftp downloads, progress of http
connection, requests, etc.. Interfering with the standard functionality
of the status bar is usually considered excessive force by a wide
majority of users.
You should drop <font> entirely since you're using stylesheet anyway.
W3C Quality Assurance tip for webmaster:
"Recommended Practices
Forget <font>, use CSS"
http://www.w3.org/QA/Tips/font-size
You can reduce the tag soup by eliminating all 119 occurences of <NOBR>
by editing a single judicious line in a stylesheet.
DU
