http://www.petesguide.com/technology/HDTV/

In KM, this page displays only :

XML Parsing Error: not well-formed
Location: http://www.petesguide.com/technology/HDTV/
Line Number 113, Column 16: <td NOWRAP BGCOLOR="#CBCB96">Frame Rate*</td>
---------------^

In Netscape 4.7, it displays useful content.

Appears to be a Mozilla based issue. Doesn't work in Mozilla, Phoenix, or KM. Worked fine in Opera, IE6, and according to you Netscape 4.x

Fails in Mozilla too. Works as a simple text page in NS 4.79,
not really as intended.

Interesting: With NS 4.79 It says on that site " the page should
display properly in a page that but it is accessible to any browser
or Internet device Trust me—you really don’t know what yo’re
missing " (Let me guess... the "u"?.)

The only broser of these four: Mozilla, K-Meleon, IE 5.5,
and Netscape 4.79, which displays the page properly is IE 5.5.
The page does not appear at all with Mozilla or KM, and only as a
simple text screen - with that quote, in Netscape 4.79.
In the correct format (IE 5.5) that quote does not appear.

There is a link to a web standards page that lists Netscape 6
an Mozilla (really?) as capable of supporting "numerous web
standards including CSS, XHTML, and the DOM (a universal
means of controlling the behavior of web pages) "

The soup thickens.
________________ Marc Stager

The page renders fine for me in K-Meleon and Mozilla 1.2. Now I do have Javascript disabled except for certain sites via policies so it may be a Javascript issue on this site.

Hmm. Asmpgmr, it must be something else that differs between our setups. I tried disabling JS and it still returns the error msg quoted above. Also tried various user agent strings -- no difference. I even tried enabling Java -- still no dice.

In Off by One and Act 10, the page's text displays OK, though the banner at the top looks even worse than it does in Netscape 4.7.

Anybody else want to try this page and report back?

Would Windows version make a difference? Win98se here.

I'm running win98se also. I have Java disabled (and no JRE on my system), Javascript disabled for all sites except one specific domain, no shockwave flash (I deleted npswf32.dll). That site renders perfectly for me in K-Meleon 0.7 and Mozilla 1.2, I see the entire article "The Digital Television Standard is Broken" and the W3C validation images and the last modification date at the end of the page. I had to look in the page source to see the Netscape 4.79 error message.

This is a long shot but trying adding this line to your prefs.js:
user_pref("browser.xul.error_pages.enabled", false);

Easy answer:

The HTML markup is not consistent with the declared DOCTYPE in the page. They are declaring XHTML Strict and yet the page is filled with deprecated tags. That's why the older browsers display it OK - they don't understand the new DOCTYPE. The new browsers actually try to render the page per the DOCTYPE and throw the error. See:

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.petesguide.com%2Ftechnology%2FHDTV%2F&charset=%28detect+automatically%29&doctype=%28detect+automatically%29

Andrew,

Then what would explain asmpgmr being able to see it in his K-Meleon when we can't?

Maybe he's using 0.6? The XHTML stuff wasn't bundled until 0.7, I believe.

No I'm using 0.7 build 700, plus the page renders fine for me in Mozilla 1.2 final (11/26/2002) as well.

I originally got same results as David; the same parsing error script
with KM and Mozilla. Both were set with HTTP = 1.1.

I changed that to 1.0, first in Mozilla, then it loaded fine.
Did same with K-Meleon and, again, page came up OK.

Puzzle is: Checked IE 5.5, and it was set "use HTTP = 1.1"
and it had no problem.

Javascript on or off had no effect.

Soup's getting real chunky.

________________ Marc Stager

>>I changed that to 1.0, first in Mozilla, then it loaded fine.
Did same with K-Meleon and, again, page came up OK.<<

Followed your lead and got the same results. Should 1.0 be the default setting?

It doesn't work in my Mozilla 1.2.1. Same error:

XML Parsing Error: not well-formed
Location: http://www.petesguide.com/technology/HDTV/
Line Number 113, Column 16: <td NOWRAP BGCOLOR="#CBCB96">Frame Rate*</td>

Disabling Javascript didn't make any difference either.

Switching to 1.0 did the trick. I'm not sure why this occurs but 1.0 should not be the default. There must be some change between 1.0 and 1.1 that causes the difference in parsing.

I'm using HTTP 1.1 in both K-Meleon and Mozilla and it works fine for me. The HTTP version only affects how pages are fetched from the server, it shouldn't affect the page content useless you're using a proxy which is somehow affecting things.

I'm not using a proxy.

Seems like this is stumping everyone. Asmpgmr there's got to be a setting or something you're using that everyone else isn't that enables you alone to see that page under http 1.1 in K-Meleon.

So far my results are completely consistent with Stagers.

I am using an ad filtering proxy, AdSubtract SE 2.42 but even if I disable its filtering the page in question still renders properly. Anyway I looked at the page source and there are no ads so that shouldn't be the issue.

Here's another thought, do you have HTTP 1.1 pipelining enabled ? That can sometimes cause problems. Also try disabling link prefetching.

Well I changed the networking pipeline pref to false. Still no go when browser set to http 1.1. And I couldn't find any pref for link fetching. By the way, what to these prefs do or mean?

This is the pref to disable link prefetching, though I doubt that's it.
user_pref("network.prefetch-next", false);

Here's a FAQ about link prefetching
http://www.mozilla.org/projects/netlib/Link_Prefetching_FAQ.html

Here's a FAQ about HTTP 1.1 pipelining
http://www.mozilla.org/projects/netlib/http/pipelining-faq.html

I can't think of anything else that would cause this page to work for me and fail for everyone else unless AdSubtract is somehow affecting things which would be surprising. The HTTP 1.0/1.1 is definitely strange. Whatever the case it's most likely a Gecko rendering engine or Necko (the networking component) problem and not specific to K-Meleon.

Maybe something to do with or not... but I can get KM to work by changing to HTTP 1.0...

...and was config'ing a new HTTPD server today (Apache on Linux) and this caught my eye (from httpd.conf) and made me think of this thread:

# The following directive disables HTTP/1.1 responses to browsers which
# are in violation of the HTTP/1.0 spec by not being able to grok a
# basic 1.1 response.
#
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0

Do you think it could be a HTTPD server mis-config'ed issue?

Nick

That wouldn't explain why I'm able to see the page just fine and others can't.

Here's the response header I get back in K-Meleon (from the about:cache-entry info)

Client: HTTP

charset: UTF-8

request-method: GET

response-head:
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8; qs=0.9
Server: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.26 mod_ssl/2.8.11 OpenSSL/0.9.6b FrontPage/4.0.4.3
Date: Mon, 09 Dec 2002 00:03:16 GMT