https://bugzilla.wikimedia.org/show_bug.cgi?id=17486
--- Comment #18 from CBM <[email protected]> 2010-01-10 13:45:45 UTC --- Re comment 13 "We should provide them an error when they produce invalid XHTML if tidy is disabled for the messages." That is made substantially more difficult by the use of parser functions inside messages. The error I reported in comment 12 only showed up for nonexistent pages in the Talk: namespace, which is why it sat unfixed for a long time. There's not going to be any practical way to test every possible control flow path through the message for XML validity. Re comment 17, "As I say, the long-term solution is to avoid XML like the plague." The proposed solution of using html5lib on the client side would help, if it accepts slightly malformed input. But of course the sort of malformed code we are serving wouldn't be well-formed HTML5 either (that is, I doubt it would pass a validator). A better long-term solution would be to fix our system to have validatable output. Of course this is not a simple thing to achieve, which is why we usually use tidy to force the output to be correct. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
