Problem with PhotoPost and Netscape

Can anyone take a look at my PhotPost pages and tell me why the header does not display correctly in Netscape? I use the same header for my entire site, but for some reason it is only affected with PhotoPost. This is with Netscape 7.

Bump?

This can be a problem perhaps:

Code:

---

<link rel=stylesheet HREF="/style.css" type-text/css>

---

It should be:

Code:

---

<link rel="stylesheet" href="/style.css" type="text/css" />

---

(note the quotes and trailing slash, and the lack of capitalization for attributes)

Your page is supposedly XHTML 1.0 Transitional, but it's not valid. Try validating your HTML and your CSS as well, and fix the errors. That may help clear up these problems.

vgarcia,

Thanks for the reply. I'll try your suggestion.

The XHTML 1.0 Transitional is actually addeed by the gallery script. I've been wondering about it. Could it affect the display of the template?

Quote:

---

Originally Posted by SVTBlackLight01

vgarcia,

Thanks for the reply. I'll try your suggestion.

The XHTML 1.0 Transitional is actually addeed by the gallery script. I've been wondering about it. Could it affect the display of the template?

---

Yes it can. Basically, many browsers have two rendering modes: "Standards" mode and "Quirks" mode. Since the XHTML 1.0 Transitional DOCTYPE was added in as the first line of your code, it throws browsers into "Standards" mode and renders according to W3C specs. Without a full DOCTYPE, browsers like IE and Opera will go into "Quirks" mode and render differently. This article should provide you with more info.

Great. I removed the XHTML 1.0 Transitional DOCTYPE line and it looks fine in NS7 now. :D I'll have to read that article when I have a little time. Can you see any problems that may be caused by removing that line?

I really appreciate the help. Thanks.

Quote:

---

Originally Posted by SVTBlackLight01

Great. I removed the XHTML 1.0 Transitional DOCTYPE line and it looks fine in NS7 now. :D I'll have to read that article when I have a little time. Can you see any problems that may be caused by removing that line?

I really appreciate the help. Thanks.

---

The version of HTML used won't be clear from being able to look at a DOCTYPE, but since you weren't valid anyway it will probably spare you a few headaches for now. :)

Thanks again. This problem has been plaguing me for quite a while. I'm glad it's at least presentable in now.