I don't know if this has been covered before, but k-meleon does not render my hotmail logon page. I get this error:

XML Parsing Error: mismatched tag. Expected: </div>.
Location: http://sn117w.snt117.mail.live.com/default.aspx?fid=1&fav=1&n=344004079&mid=31db82b8-a360-11e0-bc47-002264c20882&fv=1&cv=1&cmid=31db82b8-a360-11e0-bc47-002264c20882&csem=jo.howson%40ukgateway.net&cdid=&cfid=1&cau=1&cmad=2004%7c0%7c8CE05841A393F80%7c%7c0%7c0%7c0%7c0%7c1%7c5&cacc=1
Line Number 317, Column 7:

I am using Windows XP. Any ideas?

http://kmeleonbrowser.org/forum/search.php?3,search=hotmail,author=,page=1,match_type=ALL,match_dates=30,match_forum=ALL,match_threads=0

It seems only to affect hotmail pages in some areas/servers.

You can try with K-Meleon 1.6beta2 (stable beta) and UserAgentString set to Firefox 3.5.

p.s. I am sitting in an area that has a hotmail page that is not affected.

So my recomendation it is a guess based on past experience with other such situations and pages.



Edited 1 time(s). Last edit at 07/05/2011 09:33PM by guenter.

Thanks, Hotmail works fine with beta 6.1. Sorted!

The problem here is why the h... sites serve malformed xml pages for certain browsers.

In other words, they can't program the same page with correct XML formatting if, then, they choose what to show depending on the browser :mad:

Because this is to cry: XML Parsing Error: mismatched tag. Expected: </div> And for this I have to switch to another browsers version or change my user agent string????

Come on!

Two things wrong. A browser that bypasses these errors and bad webmasters.

Quote
JohnHell

Two things wrong. A browser that bypasses these errors and bad webmasters.

well Johnhell, for the "bad webmasters" part, direct your complaints here.

Quote
JohnHell
Because this is to cry: XML Parsing Error: mismatched tag. Expected: </div> And for this I have to switch to another browsers version or change my user agent string????

Ahhh... Why is it that to avoid XML Parsing Errors we can simply change the User Agent String? Please, don't tell me that the the User Agent String changes the Gecko Engine behaviour :s

The snippet in question is:

<p><b>If you are a new user of Cbus Member SuperSite, <a.href="Registration/Registration.aspx?fundcode=cbus">
                click here to get started</a>.

</p>

Naturally, the missing </b> throws an error.

I'm using 1.6.0b2 in W7HPx64, Default User Agent "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.17pre) Gecko K-Meleon/1.6.0". When I change to FF ("Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101130 Firefox/3.5.16"), the error is still in the page, but the engine no longer cares!

So what gives?

Gordon.

____________________
Understanding the scope of the problem is the first step on the path to true panic. [Florence Ambrose, "Freefall" 01372 January 22, 2007 http://freefall.purrsia.com/ff1400/fv01372.htm]

When reading your UA-string, such a website gives your corresponding version of page. Pages differ in some content, or sometimes page simply refuses to work if proper UA not found.

So the rendering differs.

Quote
rodocop
When reading your UA-string, such a website gives your corresponding version of page. Pages differ in some content, or sometimes page simply refuses to work if proper UA not found.

So the rendering differs.

I wish it was so simple. Here's the site/page in question:
http://www.cbussuper.com.au/member-account-login

Set my Default UA as "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.17pre) Gecko K-Meleon/1.6.0", and click "Member Super Site/Login" giving:
https://supersitenewmss.superpartners.com.au/Login.aspx?FundCode=CBUS don't worry about username/password, they're not necessary for this. Ctrl-U for the source code.

Now, set UA as FF3.5 "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101130 Firefox/3.5.16", kill the tab(s) and redo from scratch. Ctrl-U again, and compare the source.

On my machine, the error page (XML Parsing Error) shows all <script>...</script> CDATA as bright pink. The same bits in the FF3.5 page (success!) are shown in black.

Otherwise the pages appear to be the same... Just checked with WinDiff: zero differences!!!!

So the supersite page is not served differently, it is treated differently.

So what gives with the Gecko engine?

Gordon.

____________________
Understanding the scope of the problem is the first step on the path to true panic. [Florence Ambrose, "Freefall" 01372 January 22, 2007 http://freefall.purrsia.com/ff1400/fv01372.htm]

It could mean only one thing - something is classifying browsers on the server-side. I don't know exactly - what and how it does it...

OK, let's try to figure this out.

In the "View Source", what do colours signify? Some of them are easy:
<tags> are violet/purple;
"text" is blue;

But what does pink mean? For example,

<script type="text/javascript">
//<![CDATA[
if (typeof(Sys) === 'undefined') throw new Error('ASP.NET Ajax client-side framework failed to load.');
//]]>
</script>

Given that when I identify as FF3.5, getting a page that works, all the CDATA is in black?

Ummm... What exactly is "typeof(Sys)" above?

Gordon

____________________
Understanding the scope of the problem is the first step on the path to true panic. [Florence Ambrose, "Freefall" 01372 January 22, 2007 http://freefall.purrsia.com/ff1400/fv01372.htm]

I think this is OS identifier.