K-Meleon :: Bugs

Bugs : K-Meleon Forum

You can talk about issues with k-meleon here. But please, for confirmed bugs, use the bug tracker to report and give feedback on bugs.

Goto: Forum List•Message List•Search•Log In

Your Name:
Subject:

Help information

[quote=gordon451]
In https://supersitenewmss.superpartners.com.au/Login.aspx?FundCode=CBUS [color=#FF9900](it's OK, you don't need to actually log in!!!)[/color] at line 168 we find an element closing tag </p--> within a <div>.  There is no start tag <p-->, and given these two factors KM 1.6.0b2 spits the dummy, chucks a wobbly and throws an immediate fatal error as required by the XHTML standards:

[quote]When a conforming XML processor detects a fatal error it, in standards terminology, “MUST NOT” continue processing in the normal way — i.e. there is an absolute prohibition on error recovery if a well–formedness violation is detected.[/quote]from http://www.dev-archive.net/articles/xhtml.html

(Extensible Markup Language (XML) 1.0 (Fifth Edition), 1.2 Terminology, fatal error.)

The problem I (we all) have is that KM is the only browser I know of (I don't and will never use FF) that applies this strictness: Opera 11.51 doesn't.  It affects us all, because while web pages [b]should[/b] be written to standards and well-formedness [b]should[/b] be checked, these things often slip past us.  Result?  We can't use KM for these pages even though the site otherwise doesn't care [b]what[/b] browser we have.

I understand that KM is one of the "standards-compliant " browsers, which is one reason I use it.  However, sometimes some rather silly edicts must be disregarded, like this case.

Is there any way future versions can fail to spit the dummy when detecting "fatal errors" in XHTML?  Or should this be reported as a bug?

Gordon.[/quote]

K-Meleon forum is powered by Phorum.