Update XXX
authorAryeh Gregor <AryehGregor+gitcommit@gmail.com>
Sun, 10 Jul 2011 12:50:29 -0600
changeset 386 d567b8c0ba8b
parent 385 2eccea436eb6
child 387 2302c9ca1b4f
Update XXX
editcommands.html
source.html
--- a/editcommands.html	Sun Jul 10 12:47:09 2011 -0600
+++ b/editcommands.html	Sun Jul 10 12:50:29 2011 -0600
@@ -660,9 +660,16 @@
 
 <p>An <dfn id=inline-node>inline node</dfn> is a <a class=external data-anolis-spec=domcore href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-node title=concept-node>node</a> that is not a <a href=#block-node>block
 node</a>.
-
-<p class=XXX>We might not want this to key off CSS; perhaps we should be
-listing elements instead?  Needs testing.
+<!--
+The block/inline node definitions are CSS-based.  "Prohibited paragraph child"
+is conceptually similar to "block node", but based on the element name.
+Generally we want to use block/inline node when we're interested in the visual
+effect, and prohibited paragraph children when we're concerned about parsing or
+semantics.  The current spec is not always so consistent.
+-->
+
+<p class=XXX>Audit the spec to find places where we should use block node
+instead of prohibited paragraph child or vice versa (see comment).
 
 <p>An <dfn id=editing-host>editing host</dfn> is a <a class=external data-anolis-spec=domcore href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-node title=concept-node>node</a> that is either an <code class=external data-anolis-spec=domcore><a href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#element>Element</a></code> with
 a <code class=external data-anolis-spec=html title=attr-contenteditable><a href=http://www.whatwg.org/html/#attr-contenteditable>contenteditable</a></code>
--- a/source.html	Sun Jul 10 12:47:09 2011 -0600
+++ b/source.html	Sun Jul 10 12:50:29 2011 -0600
@@ -605,9 +605,16 @@
 
 <p>An <dfn>inline node</dfn> is a [[node]] that is not a <span>block
 node</span>.
-
-<p class=XXX>We might not want this to key off CSS; perhaps we should be
-listing elements instead?  Needs testing.
+<!--
+The block/inline node definitions are CSS-based.  "Prohibited paragraph child"
+is conceptually similar to "block node", but based on the element name.
+Generally we want to use block/inline node when we're interested in the visual
+effect, and prohibited paragraph children when we're concerned about parsing or
+semantics.  The current spec is not always so consistent.
+-->
+
+<p class=XXX>Audit the spec to find places where we should use block node
+instead of prohibited paragraph child or vice versa (see comment).
 
 <p>An <dfn>editing host</dfn> is a [[node]] that is either an [[element]] with
 a <code data-anolis-spec=html title=attr-contenteditable>contenteditable</code>