Browser; but not IE

  • Thread starter Thread starter Mike Ring
  • Start date Start date
Pretty hard to find out, since W3C won't even analyze the HTML without
it.
Click to expand...

Not as hard as you imagine...
It would be nice if they would adapt the analyzer to skip over this,
since it is so prevalent on the Web.
Click to expand...

....already handled: you just *tell* the validator what doctype to *use*,
as well as, if needed, the encoding to use, through the extended
interface:

http://validator.w3.org/detailed.html

And it will validate based on those settings.
 
I'd like to jump into this one if I might. I am a dedicated fan of the new
Firebird browser, and use it as my default both at home and work. However,
I was dismayed to learn that one of the sites that will not work on it is my
own! I run an online comic book, "The Journals of Simon Pariah", at
http://simonpariah.keenspace.com ...My books are generated from a freeware
program called DocCompiler, which is CSS based.
Click to expand...

I took a look and found that the pages created by DocCompiler are rendered
correctly by Mozilla/Gecko based browsers such as Mozilla Firebird.
It is, as with almost all pages that produces errors, the pages that are
broken and not the Mozilla browser.

Often the pages will not function because they rely on proprietary features
in browsers that does not follow webstandards .. in most IE.

The DocCompiler pages specificly fail (as far as I can tell from a quick 1
min read of the sourcecode) because they rely on two proprietary DOM elements.

In IE : document.all
In NS4 : document.layers

Neither are part of a W3 standard and so neither are supported by Mozilla.

This page explains more :
http://www.stopbadtherapy.com/standards.shtml

As does other pages i found doing a google search on Mozilla and
document.layers :

http://www.google.com/search?&q=mozilla document.layers

Some of them give good pointers on how to transition from nonstandard to
standard based code.

For now I suggest you mail and inform the author of DocCompiler that his
program is flawed and produces broken code.
You could CC this message and some links to pages that tell you how to
correct the errors.

And I'm sorry .. you pages need a redesign .. either from an updated version
of DocCompiler once the autor fixes the errors , or by you.

I suggest this to everyone having problems with Mozilla or other standards
based browser and webpages :
1) If you have knowledge of HTML and scripting language check the code to
see where the problem lies as a service to the author (SKIP if you don't
know HTML)
2) Report the problem to the author of the page.

Sincerely
Christian Jensen ~ CeeJay
 
I'd like to jump into this one if I might. I am a dedicated fan of the new
Firebird browser, and use it as my default both at home and work. However,
I was dismayed to learn that one of the sites that will not work on it is my
own! I run an online comic book, "The Journals of Simon Pariah", at
http://simonpariah.keenspace.com ...My books are generated from a freeware
program called DocCompiler, which is CSS based.
Click to expand...

I took a look and found that the pages created by DocCompiler are rendered
correctly by Mozilla/Gecko based browsers such as Mozilla Firebird.
It is, as with almost all pages that produces errors, the pages that are
broken and not the Mozilla browser.

Often the pages will not function because they rely on proprietary features
in browsers that does not follow webstandards .. in most IE.

The DocCompiler pages specificly fail (as far as I can tell from a quick 1
min read of the sourcecode) because they rely on two proprietary DOM elements.

In IE : document.all
In NS4 : document.layers

Neither are part of a W3 standard and so neither are supported by Mozilla.

This page explains more :
http://www.stopbadtherapy.com/standards.shtml

As does other pages i found doing a google search on Mozilla and
document.layers :

http://www.google.com/search?&q=mozilla document.layers

Some of them give good pointers on how to transition from nonstandard to
standard based code.

For now I suggest you mail and inform the author of DocCompiler that his
program is flawed and produces broken code.
You could CC this message and some links to pages that tell you how to
correct the errors.

And I'm sorry .. you pages need a redesign .. either from an updated version
of DocCompiler once the autor fixes the errors , or by you.

I suggest this to everyone having problems with Mozilla or other standards
based browser and webpages :
1) If you have knowledge of HTML and scripting language check the code to
see where the problem lies as a service to the author (SKIP if you don't
know HTML)
2) Report the problem to the author of the page.

Sincerely
Christian Jensen ~ CeeJay
 
I'd like to jump into this one if I might. I am a dedicated fan of the new
Firebird browser, and use it as my default both at home and work. However,
I was dismayed to learn that one of the sites that will not work on it is my
own! I run an online comic book, "The Journals of Simon Pariah", at
http://simonpariah.keenspace.com ...My books are generated from a freeware
program called DocCompiler, which is CSS based.
Click to expand...

I took a look and found that the pages created by DocCompiler are rendered
correctly by Mozilla/Gecko based browsers such as Mozilla Firebird.
It is, as with almost all pages that produces errors, the pages that are
broken and not the Mozilla browser.

Often the pages will not function because they rely on proprietary features
in browsers that does not follow webstandards .. in most IE.

The DocCompiler pages specificly fail (as far as I can tell from a quick 1
min read of the sourcecode) because they rely on two proprietary DOM elements.

In IE : document.all
In NS4 : document.layers

Neither are part of a W3 standard and so neither are supported by Mozilla.

This page explains more :
http://www.stopbadtherapy.com/standards.shtml

As does other pages i found doing a google search on Mozilla and
document.layers :

http://www.google.com/search?&q=mozilla document.layers

Some of them give good pointers on how to transition from nonstandard to
standard based code.

For now I suggest you mail and inform the author of DocCompiler that his
program is flawed and produces broken code.
You could CC this message and some links to pages that tell you how to
correct the errors.

And I'm sorry .. you pages need a redesign .. either from an updated version
of DocCompiler once the autor fixes the errors , or by you.

I suggest this to everyone having problems with Mozilla or other standards
based browser and webpages :
1) If you have knowledge of HTML and scripting language check the code to
see where the problem lies as a service to the author (SKIP if you don't
know HTML)
2) Report the problem to the author of the page.

Sincerely
Christian Jensen ~ CeeJay
 
This has been very helpful. Thanks. Looks like I'll have to do some more
work to make it "acceptable" across the board. Appreciate the info.

-Dominic
 
Back
Top