--- a/editcommands.html Fri Jul 08 15:03:48 2011 -0600
+++ b/editcommands.html Sun Jul 10 08:51:12 2011 -0600
@@ -38,7 +38,7 @@
<body class=draft>
<div class=head id=head>
<h1>HTML Editing Commands</h1>
-<h2 class="no-num no-toc" id=work-in-progress-—-last-update-8-july-2011>Work in Progress — Last Update 8 July 2011</h2>
+<h2 class="no-num no-toc" id=work-in-progress-—-last-update-10-july-2011>Work in Progress — Last Update 10 July 2011</h2>
<dl>
<dt>Editor
<dd>Aryeh Gregor <ayg+spec@aryeh.name>
@@ -3229,15 +3229,16 @@
parent instructions</a> to return the result of calling <code class=external data-anolis-spec=domcore title=dom-Document-createElement><a href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-document-createelement>createElement("blockquote")</a></code> on the
<code class=external data-anolis-spec=domcore title=dom-Node-ownerDocument><a href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-node-ownerdocument>ownerDocument</a></code> of <var title="">first node</var>. Let <var title="">new parent</var> be the
result.
-
- <p class=XXX>This indents on both sides, so we don't have to worry about
- directionality. Preferably we should indent only on the start side, but
- that requires care to get right in mixed-direction cases. Even once
- browsers start to support margin-start and so on, we can't use them because
- a) we have to work okay in legacy browsers and b) it doesn't help if a
- descendant block has different direction (so should be indented the other
- way). It's not clear to me that we should worry about it: most browsers
- don't, and the ones that do get it wrong.
+ <!--
+ This indents on both sides, so we don't have to worry about directionality.
+ In theory it would be better if we indented only on the start side, but that
+ requires care to get right in mixed-direction cases. Even once browsers
+ start to support margin-start and so on, we can't use them because a) we have
+ to work okay in legacy browsers and b) it doesn't help if a descendant block
+ has different direction (so should be indented the other way). So let's not
+ worry about it: most browsers don't, and the ones that do get it wrong. Just
+ indent on both sides.
+ -->
<li><a href=#fix-disallowed-ancestors>Fix disallowed ancestors</a> of <var title="">new parent</var>.
</ol>
--- a/source.html Fri Jul 08 15:03:48 2011 -0600
+++ b/source.html Sun Jul 10 08:51:12 2011 -0600
@@ -3212,15 +3212,16 @@
title=dom-Document-createElement>createElement("blockquote")</code> on the
[[ownerdocument]] of <var>first node</var>. Let <var>new parent</var> be the
result.
-
- <p class=XXX>This indents on both sides, so we don't have to worry about
- directionality. Preferably we should indent only on the start side, but
- that requires care to get right in mixed-direction cases. Even once
- browsers start to support margin-start and so on, we can't use them because
- a) we have to work okay in legacy browsers and b) it doesn't help if a
- descendant block has different direction (so should be indented the other
- way). It's not clear to me that we should worry about it: most browsers
- don't, and the ones that do get it wrong.
+ <!--
+ This indents on both sides, so we don't have to worry about directionality.
+ In theory it would be better if we indented only on the start side, but that
+ requires care to get right in mixed-direction cases. Even once browsers
+ start to support margin-start and so on, we can't use them because a) we have
+ to work okay in legacy browsers and b) it doesn't help if a descendant block
+ has different direction (so should be indented the other way). So let's not
+ worry about it: most browsers don't, and the ones that do get it wrong. Just
+ indent on both sides.
+ -->
<li><span>Fix disallowed ancestors</span> of <var>new parent</var>.
</ol>