6562 2009-02-12 08:47:14 +0000 Define parsing quirks 2010-10-04 14:31:53 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All CLOSED FIXED P2 normal --- 6563 1 hsivonen ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 23661 0 hsivonen 2009-02-12 08:47:14 +0000 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. 23662 1 ian 2009-02-12 08:48:30 +0000 I don't know what these should be. If anyone knows, please let me know. 24459 2 ian 2009-03-31 23:46:28 +0000 It would be helpful if we could get feedback from browser vendors on what quirks need to be implemented. 24501 3 hsivonen 2009-04-02 10:35:17 +0000 Thread about finding out: http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/68a093c0cce2d4a0 24736 4 hsivonen 2009-04-15 12:46:22 +0000 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. 24882 5 hsivonen 2009-04-21 10:35:52 +0000 http://alfonsopina.eresmas.net/ looks wrong without the <p><table> quirk, because it sets align on <p>. 24883 6 hsivonen 2009-04-21 12:17:07 +0000 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.)