This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6562 - Define parsing quirks
Summary: Define parsing quirks
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Blocks: 6563
  Show dependency treegraph
Reported: 2009-02-12 08:47 UTC by Henri Sivonen
Modified: 2010-10-04 14:31 UTC (History)
3 users (show)

See Also:


Description Henri Sivonen 2009-02-12 08:47:14 UTC
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.
Comment 1 Ian 'Hixie' Hickson 2009-02-12 08:48:30 UTC
I don't know what these should be. If anyone knows, please let me know.
Comment 2 Ian 'Hixie' Hickson 2009-03-31 23:46:28 UTC
It would be helpful if we could get feedback from browser vendors on what quirks need to be implemented.
Comment 3 Henri Sivonen 2009-04-02 10:35:17 UTC
Thread about finding out:
Comment 4 Henri Sivonen 2009-04-15 12:46:22 UTC
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.
Comment 5 Henri Sivonen 2009-04-21 10:35:52 UTC looks wrong without the <p><table> quirk, because it sets align on <p>.
Comment 6 Henri Sivonen 2009-04-21 12:17:07 UTC
zcorpan says:
"our options regarding <p><table> parsing are (1) having the quirk, and (2) changing Acid2"

(I agree, FWIW.)