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 18823 - html parsing algorithm possible bug wrt <p> & <div>
Summary: html parsing algorithm possible bug wrt <p> & <div>
Status: RESOLVED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-10 08:15 UTC by apavan.iitk
Modified: 2012-09-10 16:53 UTC (History)
4 users (show)

See Also:


Attachments

Description apavan.iitk 2012-09-10 08:15:37 UTC
<html>
 <head></head>
 <body>
  <p>
   <table>
    <form>
     <div>
     this is a test div
     </div>
    </form>
   </table>
  </p>
 </body>
</html>

when the above test case is parsed according to the spec
it becomes:

<html>
 <head></head>
 <body>
 <p>
  <div>
    this is a test div
  </div>

  <table>
  <form></form>
  </table>
 </p>

</body>
</html>

[in this <div> is inside <p>, while the spec explicitly states that <div> elements will be moved out of <p>]

Thus the output of the parsing algorithm violates the spec!!
Comment 1 Edward O'Connor 2012-09-10 16:53:33 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: No change.
Rationale: This aspect of the parsing algorithm is due to legacy
compatibility constraints, and thus can't be changed.