[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 86446] [test case] getElementsByTagName does not find elements
From:       David Faure <faure () kde ! org>
Date:       2004-10-14 18:28:42
Message-ID: 20041014182842.20942.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
        
http://bugs.kde.org/show_bug.cgi?id=86446        




------- Additional Comments From faure kde org  2004-10-14 20:28 -------
Thanks for the testcases, I have merged them into my regression/tests testcases. The \
css parsing thing didn't test the actual patch though (they work before and after), \
to answer whether it's ok to change the parse mode. But I found a testcase that shows \
that it's in fact not ok to do so.

When publicId=strict and systemId=transitional, the code says "for XHTML, trust \
publicId, so be strict". But with my patch it now choose transitional since hMode != \
XHtml, whereas Mozilla does choose strict indeed [this particular testcase will be \
committed as tests/parser/compatmode_xhtml_mixed.html soon].

I also couldn't change the e->setHTMLCompat() line, there are in fact many such \
lines, all activating htmlcompat from many places. So I set htmlMode to non-xhtml at \
the end of determineParseMode, when all the rest has been done (so this doesn't \
influence e.g. the CSS parsing mode).


[prev in list] [next in list] [prev in thread] [next in thread]