Re: xhtml Validation

DU <drunclear (AT) hot-R-E-M-O-V-E-mail (DOT) com> writes:

Jimbo wrote:

?xml version = "1.0"?

I suggest you get rid of this <?xml version = "1.0"?
for only 1 important and importantissimo reason:

When MSIE 6 for windows parses an html file, if the very first
instruction is a doctype in strict DTD,

A what?

it will render the page in
standards compliant rendering mode (where, for instance, the box model
is compliant with W3C CSS1 TR). Otherwise, such in this case, it will
render the page in backward compliant rendering mode, therefore using
an invalid and incorrect CSS1 box model.

Which spares you the trouble to compare the results with versions prior
to 6, spares you the trouble to solve a couple of bugs IE6 only sports
in so-called 'standards compliant' mode and spares you the trouble of
double-checking what IE6 does when 3rd party software like ad-blocking
proxies insert anything before the docHype declaration.

Of course, since MicrosoftIE cannot handle XHTML in the first place, we're
talking about serving XHTML syntax as text/html. The newsgroup
discussing voodoo is all the way down the corridor, 2nd door to the
left.


--
"In America the young are always ready to give to those who are older
than themselves the full benefits of their inexperience."
--Oscar Wilde

Eric B. Bednarz wrote:

DU <drunclear (AT) hot-R-E-M-O-V-E-mail (DOT) com> writes:


Jimbo wrote:


?xml version = "1.0"?

I suggest you get rid of this <?xml version = "1.0"?
for only 1 important and importantissimo reason:

When MSIE 6 for windows parses an html file, if the very first
instruction is a doctype in strict DTD,


A what?

doctype declaration: public identifier and system identifier.

it will render the page in
standards compliant rendering mode (where, for instance, the box model
is compliant with W3C CSS1 TR). Otherwise, such in this case, it will
render the page in backward compliant rendering mode, therefore using
an invalid and incorrect CSS1 box model.


Which spares you the trouble to compare the results with versions prior
to 6, spares you the trouble to solve a couple of bugs IE6 only sports
in so-called 'standards compliant' mode and spares you the trouble of
double-checking what IE6 does when 3rd party software like ad-blocking
proxies insert anything before the docHype declaration.

Of course, since MicrosoftIE cannot handle XHTML in the first place, we're
talking about serving XHTML syntax as text/html. The newsgroup
discussing voodoo is all the way down the corridor, 2nd door to the
left.

I tried to bring up a constructive and positive reply along with
suggestions to the OP. If your concern is about previous versions of
MSIE prior to version 6, then there are well known workarounds (tested,
verified and working) for MSIE 5.x incorrect box model.

Box Model Hack
http://tantek.com/CSS/Examples/boxmodelhack.html

Modified Simplified Box Model Hack
http://www.info.com.ph/~etan/w3panth...ifiedsbmh.html

AvoidingHacks
http://css-discuss.incutio.com/?page=AvoidingHacks

etc..

But before we discuss MSIE 5.x incorrect box model and how to
compensate, adjusting the source code, it should be known that a wide
majority of independent sources converge to say that more than 50% of
all web browsers in use on the web today is MSIE 6 for windows. if MSIE
6 is compliant with W3C web standards in a wide, large part, then why
not conform webpages to valid markup syntax, CSS1 properties and DOM1
attributes and methods?

It is in the best interests of web designers to make their page trigger
standards compliant rendering mode in MSIE 6 for windows for hundreds of
reasons. Many organizations and professional web designers have insisted
during months and years that Microsoft fix its broken box model. Now,
that it has been fixed in version 6, it's up to so-called web designers
to follow up on their own request and to be consequent, coherent.
Anything else is just jabbering cretinism dancing in colorized obscurantism.

DU
--
Javascript and Browser bugs:
http://www10.brinkster.com/doctorunclear/
- Resources, help and tips for Netscape 7.x users and Composer
- Interactive demos on Popup windows, music (audio/midi) in Netscape 7.x
http://www10.brinkster.com/doctorunc...e7Section.html