This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The spec currently has "XXX quirks" comments suggesting that parts of the tree building algorithm will behave differently in the quirks mode. Those differences should either go away or be hoisted out of comments.
I don't know what these should be. If anyone knows, please let me know.
It would be helpful if we could get feedback from browser vendors on what quirks need to be implemented.
Thread about finding out: http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/68a093c0cce2d4a0
I think I'm summarizing correctly if I say that the only issue left is <p><table> and in that case it would be safe to have the quirk but nicer to eliminate the quirk one way or the other. However, eliminating the quirk would require further research or at least analyzing existing data more carefully.
http://alfonsopina.eresmas.net/ looks wrong without the <p><table> quirk, because it sets align on <p>.
zcorpan says: "our options regarding <p><table> parsing are (1) having the quirk, and (2) changing Acid2" http://lists.w3.org/Archives/Public/public-html/2009Apr/0197.html (I agree, FWIW.)