Skip to content
Permalink
Browse files
[ct] (2) As far as I can tell, the table sections should also generat…
…e implied end tags. No?

git-svn-id: http://svn.whatwg.org/webapps@965 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jun 28, 2007
1 parent 7e6dfce commit 7d6ac6dedd38ff42847757ac7313ade33b31feab
Showing with 23 additions and 12 deletions.
  1. +11 −4 index
  2. +12 −8 source
15 index
@@ -36019,9 +36019,13 @@ function receiver(e) {
<code><a href="#dd">dd</a></code> element, a <code><a
href="#dt">dt</a></code> element, an <code><a href="#li">li</a></code>
element, a <code><a href="#p">p</a></code> element, a <code><a
href="#td">td</a></code> element, a <code><a href="#th">th</a></code>
element, or a <code><a href="#tr">tr</a></code> element, the UA must act
as if an end tag with the respective tag name had been seen and then <a
href="#tbody">tbody</a></code> element, a <code><a
href="#td">td</a></code> element, a <code><a
href="#tfoot0">tfoot</a></code> element, a <code><a
href="#th">th</a></code> element, a <code><a
href="#thead0">thead</a></code> element, a <code><a
href="#tr">tr</a></code> element, the UA must act as if an end tag with
the respective tag name had been seen and then <a
href="#generate">generate implied end tags</a> again.

<p>The step that requires the UA to generate implied end tags but lists an
@@ -36782,8 +36786,11 @@ simplified explanation instead:
href="#dd">dd</a></code> element, a <code><a
href="#dt">dt</a></code> element, an <code><a
href="#li">li</a></code> element, a <code><a href="#p">p</a></code>
element, a <code><a href="#td">td</a></code> element, a <code><a
element, a <code><a href="#tbody">tbody</a></code> element, a
<code><a href="#td">td</a></code> element, a <code><a
href="#tfoot0">tfoot</a></code> element, a <code><a
href="#th">th</a></code> element, a <code><a
href="#thead0">thead</a></code> element, a <code><a
href="#tr">tr</a></code> element, the <code><a
href="#body0">body</a></code> element, or the <code><a
href="#html">html</a></code> element, then this is a <a
20 source
@@ -33138,10 +33138,12 @@ function receiver(e) {
<p>When the steps below require the UA to <dfn>generate implied end
tags</dfn>, then, if the <span>current node</span> is a
<code>dd</code> element, a <code>dt</code> element, an
<code>li</code> element, a <code>p</code> element, a <code>td</code>
element, a <code>th</code> element, or a <code>tr</code> element,
the UA must act as if an end tag with the respective tag name had
been seen and then <span>generate implied end tags</span> again.</p>
<code>li</code> element, a <code>p</code> element, a
<code>tbody</code> element, a <code>td</code> element, a
<code>tfoot</code> element, a <code>th</code> element, a
<code>thead</code> element, a <code>tr</code> element, the UA must
act as if an end tag with the respective tag name had been seen and
then <span>generate implied end tags</span> again.</p>

<p>The step that requires the UA to generate implied end tags but
lists an element to exclude from the process, then the UA must
@@ -33938,10 +33940,12 @@ simplified explanation instead:
<p>Otherwise, if there is a node in the <span>stack of open
elements</span> that is not either a <code>dd</code> element,
a <code>dt</code> element, an <code>li</code> element, a
<code>p</code> element, a <code>td</code> element, a
<code>th</code> element, a <code>tr</code> element, the
<code>body</code> element, or the <code>html</code> element,
then this is a <span>parse error</span>.</li>
<code>p</code> element, a <code>tbody</code> element, a
<code>td</code> element, a <code>tfoot</code> element, a
<code>th</code> element, a <code>thead</code> element, a
<code>tr</code> element, the <code>body</code> element, or the
<code>html</code> element, then this is a <span>parse
error</span>.</li>

<p>Change the <span>insertion mode</span> to "<span
title="insertion mode: after body">after body</span>".</p>

0 comments on commit 7d6ac6d

Please sign in to comment.