Permalink
Browse files

[e] (0) Remove a paragraph from the W3C copy on chair request.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=13903
Affected topics: HTML

git-svn-id: http://svn.whatwg.org/webapps@6994 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
1 parent e8ef4ba commit 51d1d778d7e0b4a0d35a153714401c36a244efca @Hixie Hixie committed Feb 14, 2012
Showing with 52 additions and 8 deletions.
  1. +17 −3 complete.html
  2. +17 −3 index
  3. +18 −2 source
View
@@ -240,7 +240,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 13 February 2012</h2>
+ <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 14 February 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -1494,6 +1494,12 @@ <h6 class=no-toc id=how-do-the-whatwg-and-w3c-specifications-differ?><span class
group chair request from February
2012</a>.</li><!--HIDDENARIA--><!--FORK-->
+ <li>The W3C HTML specification does not define the term <a href=#rel-sidebar-hyperlink title=rel-sidebar-hyperlink>sidebar hyperlink</a>, forcing the
+ definition of the <code title=rel-sidebar>sidebar</code> link
+ type in the microformats wiki to rely on this copy of the spec
+ instead, because of a <a href=http://lists.w3.org/Archives/Public/public-html/2012Jan/0131.html>working
+ group chair decision from November 2011</a>.</li>
+
</ul><p>The following sections are only published in the WHATWG
specifications and are not currently available anywhere else:</p>
@@ -54603,14 +54609,22 @@ <h4 id=following-hyperlinks-0><span class=secno>4.12.3 </span>Following hyperlin
new <a href=#browsing-context>browsing context</a>, it must be navigated with
<a href=#replacement-enabled>replacement enabled</a>.</p>
-<!-- if http://www.w3.org/Bugs/Public/show_bug.cgi?id=11183 is ever reverted, then change the dfn below back into a span -->
-<!-- in the meantime, the definition of rel=sidebar in the wiki says that it's a "sidebar hyperlink" --> <!--!-->
+<!--FORK--><!--!-->
+<!-- If these bugs are ever reverted:
+ https://www.w3.org/Bugs/Public/show_bug.cgi?id=11183
+ https://www.w3.org/Bugs/Public/show_bug.cgi?id=13903
+ ...then change the dfn below back into a span.
+ In the meantime, the definition of rel=sidebar in the wiki says
+ that it's a "sidebar hyperlink", and links to the WHATWG spec, so
+ that everything remains well-defined, at least if you ignore the
+ W3C specs. -->
<p>Otherwise, if the hyperlink is a <dfn id=rel-sidebar-hyperlink title=rel-sidebar-hyperlink>sidebar hyperlink</dfn> and the user
agent implements a feature that can be considered a <a href=#secondary-browsing-context>secondary
browsing context</a>, such a <a href=#secondary-browsing-context>secondary browsing
context</a> may be selected as the browsing context to be
navigated.</p>
+
<p>Otherwise, if the element is an <code><a href=#the-a-element>a</a></code> or
<code><a href=#the-area-element>area</a></code> element with no <code title=attr-hyperlink-target><a href=#attr-hyperlink-target>target</a></code> attribute, but the
<code><a href=#document>Document</a></code> contains a <code><a href=#the-base-element>base</a></code> element with a
View
@@ -240,7 +240,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 13 February 2012</h2>
+ <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 14 February 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -1494,6 +1494,12 @@
group chair request from February
2012</a>.</li><!--HIDDENARIA--><!--FORK-->
+ <li>The W3C HTML specification does not define the term <a href=#rel-sidebar-hyperlink title=rel-sidebar-hyperlink>sidebar hyperlink</a>, forcing the
+ definition of the <code title=rel-sidebar>sidebar</code> link
+ type in the microformats wiki to rely on this copy of the spec
+ instead, because of a <a href=http://lists.w3.org/Archives/Public/public-html/2012Jan/0131.html>working
+ group chair decision from November 2011</a>.</li>
+
</ul><p>The following sections are only published in the WHATWG
specifications and are not currently available anywhere else:</p>
@@ -54603,14 +54609,22 @@ fur
new <a href=#browsing-context>browsing context</a>, it must be navigated with
<a href=#replacement-enabled>replacement enabled</a>.</p>
-<!-- if http://www.w3.org/Bugs/Public/show_bug.cgi?id=11183 is ever reverted, then change the dfn below back into a span -->
-<!-- in the meantime, the definition of rel=sidebar in the wiki says that it's a "sidebar hyperlink" --> <!--!-->
+<!--FORK--><!--!-->
+<!-- If these bugs are ever reverted:
+ https://www.w3.org/Bugs/Public/show_bug.cgi?id=11183
+ https://www.w3.org/Bugs/Public/show_bug.cgi?id=13903
+ ...then change the dfn below back into a span.
+ In the meantime, the definition of rel=sidebar in the wiki says
+ that it's a "sidebar hyperlink", and links to the WHATWG spec, so
+ that everything remains well-defined, at least if you ignore the
+ W3C specs. -->
<p>Otherwise, if the hyperlink is a <dfn id=rel-sidebar-hyperlink title=rel-sidebar-hyperlink>sidebar hyperlink</dfn> and the user
agent implements a feature that can be considered a <a href=#secondary-browsing-context>secondary
browsing context</a>, such a <a href=#secondary-browsing-context>secondary browsing
context</a> may be selected as the browsing context to be
navigated.</p>
+
<p>Otherwise, if the element is an <code><a href=#the-a-element>a</a></code> or
<code><a href=#the-area-element>area</a></code> element with no <code title=attr-hyperlink-target><a href=#attr-hyperlink-target>target</a></code> attribute, but the
<code><a href=#document>Document</a></code> contains a <code><a href=#the-base-element>base</a></code> element with a
View
@@ -233,6 +233,14 @@
group chair request from February
2012</a>.</li><!--HIDDENARIA--><!--FORK-->
+ <li>The W3C HTML specification does not define the term <span
+ title="rel-sidebar-hyperlink">sidebar hyperlink</span>, forcing the
+ definition of the <code title="rel-sidebar">sidebar</code> link
+ type in the microformats wiki to rely on this copy of the spec
+ instead, because of a <a
+ href="http://lists.w3.org/Archives/Public/public-html/2012Jan/0131.html">working
+ group chair decision from November 2011</a>.</li>
+
</ul>
<p>The following sections are only published in the WHATWG
@@ -63703,14 +63711,22 @@ fur
new <span>browsing context</span>, it must be navigated with
<span>replacement enabled</span>.</p>
-<!-- if http://www.w3.org/Bugs/Public/show_bug.cgi?id=11183 is ever reverted, then change the dfn below back into a span -->
-<!-- in the meantime, the definition of rel=sidebar in the wiki says that it's a "sidebar hyperlink" --> <!--!-->
+<!--END w3c-html--><!--FORK--><!--!-->
+<!-- If these bugs are ever reverted:
+ https://www.w3.org/Bugs/Public/show_bug.cgi?id=11183
+ https://www.w3.org/Bugs/Public/show_bug.cgi?id=13903
+ ...then change the dfn below back into a span.
+ In the meantime, the definition of rel=sidebar in the wiki says
+ that it's a "sidebar hyperlink", and links to the WHATWG spec, so
+ that everything remains well-defined, at least if you ignore the
+ W3C specs. -->
<p>Otherwise, if the hyperlink is a <dfn
title="rel-sidebar-hyperlink">sidebar hyperlink</dfn> and the user
agent implements a feature that can be considered a <span>secondary
browsing context</span>, such a <span>secondary browsing
context</span> may be selected as the browsing context to be
navigated.</p>
+<!--START w3c-html-->
<p>Otherwise, if the element is an <code>a</code> or
<code>area</code> element with no <code

0 comments on commit 51d1d77

Please sign in to comment.