18367 2012-07-23 23:07:54 +0000 Spec causes continuous loop 2012-10-21 22:25:34 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED FIXED P2 normal --- 1 mridul silviapfeiffer1 mike mridul public-html-admin public-html-wg-issue-tracking silviapfeiffer1 public-html-bugzilla oldest_to_newest 71335 0 mridul 2012-07-23 23:07:54 +0000 Consider the stack of open elements to be : html, body, form, table, tbody (form being present is irrelevant to this imo). The current insertion mode is IN TABLE BODY as expected. When the next token being consumed is end tag p, then the parser will go into an infinite loop. IN TABLE BODY will delegate to IN TABLE, which will delegate to IN BODY with foster parenting enabled. The end tag p will cause a 'act as if' start token for p (since there is no P in button scope) - which will go through same flow to end in IN BODY with foster parenting enabled. The resulting insertion of p tag due to then token will get foster parent'ed - and so, on return, reconsumption of end tag p will essentially cause the same loop to be repeated indefinitely. If our understanding of the spec, as detailed above, is incorrect - that would be great ! Please do let us know. Thanks, Mridul 71386 1 mridul 2012-07-24 14:34:41 +0000 Looks like even when foster parent'ed, the node to be inserted must be pushed to open elements stack - might be good to clarify this since we figured it out via trial and error. Closing bug. 76271 2 silviapfeiffer1 2012-10-15 05:09:24 +0000 Reopening, so I can apply the patch of cloned WHATWG bug 18473 to the W3C spec. 76852 3 silviapfeiffer1 2012-10-21 22:25:34 +0000 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-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/2758f0e460f26cdf2fb510e26062eb7f5c17f171 Rationale: Adopted WHATWG patch