In https://supersitenewmss.superpartners.com.au/Login.aspx?FundCode=CBUS (it's OK, you don't need to actually log in!!!)
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:
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.
(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 should
be written to standards and well-formedness should
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 what
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?
Gigabyte H61M-USB3-B3 r2.0, I5-2400 3.10GHz, 4GB RAM; W7HPx64 SP1, Lotus SmartSuite 9.8, K-Meleon 76RC, Pale Moon 26.4.1, IE11, Clyton email 15.0, Foxit Reader 126.96.36.1996, PaintShop Pro 6.02, ZAM Free 2.74, SuRun 188.8.131.52, VoodooShield 3.59b
"Learning is not compulsory. Neither is survival." Dr. W. Edwards Deming.
Edited 1 time(s). Last edit at 10/17/2011 02:11PM by gordon451.