Why does Firefox fail to enterpret html sometimes?

Here's an example of a page that my copy of Firefox is not
entepreting:

http://www.cocosee.com/destinations

I just see html in the browser window.

Thanks

Rich
To email me remove the dog from my address.

In article <424daa44.37785764 (AT) news (DOT) individual.net>,
AdogAnotes3 (AT) aol (DOT) com (Rich) wrote:

http://www.cocosee.com/destinations

Maybe because the file doesn't have a .htm suffix (or .html or .shtml)

Al.

--
Alan Cole. E-mail: justal at lineone dot net
http://www.forces-of-nature.co.uk [Coastal Sports]
http://www.pixelwave.co.uk [Website Design, hosting and promotion]

Because you have no doctype specified for one reason.

-------------------------------------------------------------------------------
"Rich" <AdogAnotes3 (AT) aol (DOT) com> wrote

Here's an example of a page that my copy of Firefox is not
entepreting:

http://www.cocosee.com/destinations

I just see html in the browser window.

Thanks

Rich
To email me remove the dog from my address.

On 1-Apr-2005, AdogAnotes3 (AT) aol (DOT) com (Rich) wrote:

Here's an example of a page that my copy of Firefox is not
entepreting:

http://www.cocosee.com/destinations

I just see html in the browser window.

Thanks

Checking the html with a validator it reports 20
errors, not uncommon with stuff produced by MS$ FP.
MS browsers are incredibly tolerant of errors produced
by FP. I abandoned FP in disgust many years
ago.

CSE HTML Validator Professional v4.03 (Registered)
Checking "C:\Documents and Settings\********\Desktop\destinations.htm"
(15935 bytes).
File date is 01 April 2005 at 21:53:46.
File validated on 01 April 2005 at 21:54:45.

Number of lines checked: 313 in 0.79 seconds
Number of programs run: 387
Number of lines in HTML file: 360 (86.9% of lines checked)
Number of lines ignored: 47
Number of character entities: 57
Number of tags: 253
Number of closing tags: 187 (73.9% of tags closed)
Number of <% ... %> sections: 0
Number of HTML comments: 8

Number of validator comments: 7
Number of messages: 6
Number of errors: 20 (first in line 14) <<-----<<------
Number of warnings: 20 (first in line 63)

He may have serious problems getting ranked.
I see it's also using CSS, bet if I validated the CSS as
well it would also have loads of errors.

Wouldn't link to this, myself, but it's up to you.

Actually that page will not validate at all for HTML since no doctype is
specified.

And the errors you see have nothing to do with Frontpage.

-------------------------------------------------------------------------------
<ato_zee (AT) hotmail (DOT) com> wrote

On 1-Apr-2005, AdogAnotes3 (AT) aol (DOT) com (Rich) wrote:

Here's an example of a page that my copy of Firefox is not
entepreting:

http://www.cocosee.com/destinations

I just see html in the browser window.

Thanks

Checking the html with a validator it reports 20
errors, not uncommon with stuff produced by MS$ FP.
MS browsers are incredibly tolerant of errors produced
by FP. I abandoned FP in disgust many years
ago.

CSE HTML Validator Professional v4.03 (Registered)
Checking "C:\Documents and Settings\********\Desktop\destinations.htm"
(15935 bytes).
File date is 01 April 2005 at 21:53:46.
File validated on 01 April 2005 at 21:54:45.

Number of lines checked: 313 in 0.79 seconds
Number of programs run: 387
Number of lines in HTML file: 360 (86.9% of lines checked)
Number of lines ignored: 47
Number of character entities: 57
Number of tags: 253
Number of closing tags: 187 (73.9% of tags closed)
Number of <% ... %> sections: 0
Number of HTML comments: 8

Number of validator comments: 7
Number of messages: 6
Number of errors: 20 (first in line 14) <<-----<<------
Number of warnings: 20 (first in line 63)

He may have serious problems getting ranked.
I see it's also using CSS, bet if I validated the CSS as
well it would also have loads of errors.

Wouldn't link to this, myself, but it's up to you.

Rich wrote:

Here's an example of a page that my copy of Firefox is not
entepreting:

http://www.cocosee.com/destinations

I just see html in the browser window.

This is not a problem with firefox. The web server is returning the
Content-Type as text/plain in the HTTP header. There is nothing special
about html, pdf, jpeg, they are just streams of bytes, what governs what
type they are is the MIME header type sent by the server.

----------------------
http://www.abcseo.com/

Rich wrote:

Here's an example of a page that my copy of Firefox is not
entepreting:

http://www.cocosee.com/destinations

I just see html in the browser window.

This is not a problem with firefox. The web server is returning the
Content-Type as text/plain in the HTTP header. There is nothing special
about html, pdf, jpeg, they are just streams of bytes, what governs what
type they are is the MIME header type sent by the server.

----------------------
http://www.abcseo.com/

On Fri, 01 Apr 2005 20:10:20 GMT, AdogAnotes3 (AT) aol (DOT) com (Rich) wrote:

Here's an example of a page that my copy of Firefox is not
entepreting:

http://www.cocosee.com/destinations

I just see html in the browser window.

Thanks

Rich
To email me remove the dog from my address.

I won't work simply because it fails validation.
Fix that, and your problems should go, as long as you fixed any box
model bugs (if you are using them) and most of those errors should be
handled by CSS anyway.

And don't forget to add a DTD

http://www.htmlhelp.com/cgi-bin/vali...s&warnings=yes

Valid html makes cross browser compatability easier.

HTH
Paul


http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

On 1-Apr-2005, "Windsun" <wind-sun (AT) earthlink (DOT) net> wrote:

Actually that page will not validate at all for HTML since no doctype is
specified.

And the errors you see have nothing to do with Frontpage.

But it displays ok with MS$ IE.

davidof wrote:

Rich wrote:

Here's an example of a page that my copy of Firefox is not
entepreting:

http://www.cocosee.com/destinations

I just see html in the browser window.

This is not a problem with firefox. The web server is returning the
Content-Type as text/plain in the HTTP header. There is nothing special
about html, pdf, jpeg, they are just streams of bytes, what governs what
type they are is the MIME header type sent by the server.

Internet Explorer, on the other hand, *does* have a problem.
It is displaying something with Content-Type: text/plain as HTML.
That's a bug, and a serious one. It can fool unskilled web authors
into thinking that they are making HTML webpages when they are not.