https://bugzilla.wikimedia.org/show_bug.cgi?id=54617
--- Comment #2 from Brion Vibber <[email protected]> --- So the main reason we went with Tidy in the first place I think was to ensure that we had well-formed (X)HTML output, so XML parsers wouldn't die and browsers wouldn't do exciting things if you had a stray </div> somewhere. The core parser tries to do some HTML cleanup, but it was never very complete. Possibilities include: a) Fix the HTML fixups in the core parser, and make sure non-Tidy output is compatible with the current Tidy output b) Replace Tidy with another tool that's less annoying c) Replace the core parser with something that already outputs valid HTML5 (such as Parsoid) Long-term I like c) but I don't think we're there yet. :) a) and b) are the things I'd recommend looking at if we really want to kill tidy in the short/medium term. -- 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
