- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 22 Jul 2011 07:01:51 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv9241
Modified Files:
Overview.html
Log Message:
New feature: <a download='filename'>. (whatwg r6318)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5048
retrieving revision 1.5049
diff -u -d -r1.5048 -r1.5049
--- Overview.html 20 Jul 2011 22:28:37 -0000 1.5048
+++ Overview.html 22 Jul 2011 07:01:47 -0000 1.5049
@@ -318,7 +318,7 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="editor-s-draft-20-july-2011">Editor's Draft 20 July 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-22-july-2011">Editor's Draft 22 July 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -464,7 +464,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 20 July 2011 Editor's Draft.
+ This specification is the 22 July 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -16672,10 +16672,11 @@
</nav></pre>
</div><div class="impl">
- <p>The <code title="attr-hyperlink-href"><a href="#attr-hyperlink-href">href</a></code>, <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code>
- attributes affect what
- happens when users <a href="#following-hyperlinks" title="following hyperlinks">follow
- hyperlinks</a> created using the <code><a href="#the-a-element">a</a></code> element. The
+ <p>The <code title="attr-hyperlink-href"><a href="#attr-hyperlink-href">href</a></code>,
+ <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code>,
+ attributes affect what happens when users <a href="#following-hyperlinks" title="following
+ hyperlinks">follow hyperlinks</a>
+ created using the <code><a href="#the-a-element">a</a></code> element. The
<code title="attr-hyperlink-rel"><a href="#attr-hyperlink-rel">rel</a></code>, <code title="attr-hyperlink-media"><a href="#attr-hyperlink-media">media</a></code>, <code title="attr-hyperlink-hreflang"><a href="#attr-hyperlink-hreflang">hreflang</a></code>, and <code title="attr-hyperlink-type"><a href="#attr-hyperlink-type">type</a></code> attributes may be used to
indicate to the user the likely nature of the target resource before
the user follows the link.</p>
@@ -16687,7 +16688,7 @@
<ol><li><p>If the <code title="event-click"><a href="#event-click">click</a></code> event in
question is not <a href="#concept-events-trusted" title="concept-events-trusted">trusted</a>
(i.e. a <code title="dom-click"><a href="#dom-click">click()</a></code> method call was the
- reason for the event being dispatched), and the <code><a href="#the-a-element">a</a></code>
+ reason for the event being dispatched), and either the <code><a href="#the-a-element">a</a></code>
element's <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code>
attribute is present and applying <a href="#the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name">the rules for choosing a
browsing context given a browsing context name</a>, using the
@@ -16722,10 +16723,11 @@
</ol></li>
<li><p>Finally, the user agent must <a href="#following-hyperlinks" title="following
- hyperlinks">follow the hyperlink</a> created by the
- <code><a href="#the-a-element">a</a></code> element. If the steps above defined a <var><a href="#hyperlink-suffix">hyperlink
- suffix</a></var>, then take that into account when following the
- hyperlink.</li>
+ hyperlinks">follow the hyperlink</a>
+ created by the <code><a href="#the-a-element">a</a></code> element, as determined by
+ any expressed user preference. If the steps above defined a
+ <var><a href="#hyperlink-suffix">hyperlink suffix</a></var>, then take that into account when
+ following or downloading the hyperlink.</li>
</ol></div><dl class="domintro"><dt><var title="">a</var> . <code title="dom-a-text"><a href="#dom-a-text">text</a></code></dt>
@@ -16737,7 +16739,8 @@
</dl><div class="impl">
- <p>The IDL attributes <dfn id="dom-a-href" title="dom-a-href"><code>href</code></dfn>,
+ <p>The IDL attributes
+ <dfn id="dom-a-href" title="dom-a-href"><code>href</code></dfn>,
<dfn id="dom-a-target" title="dom-a-target"><code>target</code></dfn>, <dfn id="dom-a-rel" title="dom-a-rel"><code>rel</code></dfn>, <dfn id="dom-a-media" title="dom-a-media"><code>media</code></dfn>, <dfn id="dom-a-hreflang" title="dom-a-hreflang"><code>hreflang</code></dfn>, and <dfn id="dom-a-type" title="dom-a-type"><code>type</code></dfn>, must
<a href="#reflect">reflect</a> the respective content attributes of the same
name.</p>
@@ -28212,12 +28215,13 @@
all in CSS pixels.<div class="impl">
<p>When user agents allow users to <a href="#following-hyperlinks" title="following
- hyperlinks">follow hyperlinks</a> created using the
- <code><a href="#the-area-element">area</a></code> element, as described in the next section, the
+ hyperlinks">follow hyperlinks</a>
+ created using the <code><a href="#the-area-element">area</a></code> element, as described in the
+ next section, the
<code title="attr-hyperlink-href"><a href="#attr-hyperlink-href">href</a></code>,
- <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code>
- attributes decide how the
- link is followed. The <code title="attr-hyperlink-rel"><a href="#attr-hyperlink-rel">rel</a></code>,
+ <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code>,
+ attributes decide how the link is followed.
+ The <code title="attr-hyperlink-rel"><a href="#attr-hyperlink-rel">rel</a></code>,
<code title="attr-hyperlink-media"><a href="#attr-hyperlink-media">media</a></code>, <code title="attr-hyperlink-hreflang"><a href="#attr-hyperlink-hreflang">hreflang</a></code>, and <code title="attr-hyperlink-type"><a href="#attr-hyperlink-type">type</a></code> attributes may be used to
indicate to the user the likely nature of the target resource before
the user follows the link.</p>
@@ -28243,9 +28247,10 @@
<code><a href="#invalid_access_err">INVALID_ACCESS_ERR</a></code> exception and abort these
steps.</li>
- <li>Otherwise, the user agent must <a href="#following-hyperlinks" title="following
- hyperlinks">follow the hyperlink</a> created by the
- <code><a href="#the-area-element">area</a></code> element, if any.</li>
+ <li><p>Otherwise, the user agent must <a href="#following-hyperlinks" title="following
+ hyperlinks">follow the hyperlink</a>
+ created by the <code><a href="#the-area-element">area</a></code> element, if any, and as determined by
+ any expressed user preference.</li>
</ol><p>The IDL attributes <dfn id="dom-area-alt" title="dom-area-alt"><code>alt</code></dfn>, <dfn id="dom-area-coords" title="dom-area-coords"><code>coords</code></dfn>, <dfn id="dom-area-href" title="dom-area-href"><code>href</code></dfn>, <dfn id="dom-area-target" title="dom-area-target"><code>target</code></dfn>,
<dfn id="dom-area-rel" title="dom-area-rel"><code>rel</code></dfn>, <dfn id="dom-area-media" title="dom-area-media"><code>media</code></dfn>, <dfn id="dom-area-hreflang" title="dom-area-hreflang"><code>hreflang</code></dfn>, and <dfn id="dom-area-type" title="dom-area-type"><code>type</code></dfn>, each must
@@ -45994,19 +45999,26 @@
</li>
- <li><p>If the document's out-of-band metadata (e.g. HTTP headers),
- not counting any <a href="#content-type" title="Content-Type">type information</a>
- (such as the Content-Type HTTP header), requires some sort of
- processing that will not affect the browsing context, then perform
- that processing and abort these steps.</p>
+ <li>
+
+ <p>If the document's out-of-band metadata (e.g. HTTP headers), not
+ counting any <a href="#content-type" title="Content-Type">type information</a>
+ (such as the Content-Type HTTP header), requires some sort of
+ processing that will not affect the browsing context, then perform
+ that processing and abort these steps.</p>
+
+ <div class="note">
+ <p>Such processing might be triggered by, amongst other things, the
+ following:</p>
+ <ul class="brief"><li>HTTP status codes (e.g. 204 No Content or 205 Reset Content)</li>
+ <li>Network errors (e.g. the network interface being unavailable)</li>
+ <li>Cryptographic protocol failures (e.g. an incorrect TLS certificate)</li>
+
+
+
+
+ </ul></div>
- <div class="note">
- <p>Such processing might be triggered by, amongst other things, the
- following:</p>
- <ul class="brief"><li>HTTP status codes (e.g. 204 No Content or 205 Reset Content)</li>
- <li>HTTP Content-Disposition headers</li>
- <li>Network errors</li>
- </ul></div>
<p>HTTP 401 responses that do not include a challenge recognized
Received on Friday, 22 July 2011 07:01:52 UTC