Comment #2 on issue 8188 by 0.fractalus: My website appears Empty on Chrome
(and works perfectly with other browsers)
http://code.google.com/p/chromium/issues/detail?id=8188
Appears to be a parser bug... Looking at the source, there's things like
this all
over the place:
<style type="text/css">
/*<![CDATA[*/
<!--
.style24 {
color: #999999;
font-family: Arial, Helvetica, sans-serif;
font-size: 18px;
}
.style36 {font-size: 16px}
-->
/*]]>*/
</style>
Appears that the attempt at making the XHTML parser in mozilla play nice
has been
reduced to WebKit's parser going "huh? i see <!CDATA[, but no ]]>!
I'd attempt removing the CDATA's all over the place because there's a few
things that
you don't really need them for. here's why:
- the SCRIPT tag (xml: script) defines its content in the DTD as "CDATA",
so there's
no reason to have special stuff.
- the STYLE tag (xml: style) defines its content to be "CDATA" as well, so
again
there's no reason to have special commented-CDATA tags.
I belive the reason they're there is because the author (or generator/HTML
Tidy?) is
attempting to be "Backwards Compatible" with non-styling/Non-Js pages. In
reality,
there's no reason to. Any browser today (I.e. Ie5.5+) that honors the HTML4
DTD or at
least XHTML1.0 DTD should know that you dont parse the characters in SCRIPT
and STYLE
tags.
Also, why do i say that its a parser bug? because it gets to the HEAD and
doesn't see
anything in the Inspector, just an odd BODY tag.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
