[html5] r5684 - [e] (0) Refactor form submission browsing context details. This in theory didn't [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Nov 29 16:41:20 PST 2010
Author: ianh
Date: 2010-11-29 16:41:19 -0800 (Mon, 29 Nov 2010)
New Revision: 5684
Modified:
complete.html
index
source
Log:
[e] (0) Refactor form submission browsing context details. This in theory didn't change anything.
Modified: complete.html
===================================================================
--- complete.html 2010-11-29 22:56:34 UTC (rev 5683)
+++ complete.html 2010-11-30 00:41:19 UTC (rev 5684)
@@ -214,7 +214,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1>Web Applications 1.0</h1>
- <h2 class="no-num no-toc">Draft Standard — 29 November 2010</h2>
+ <h2 class="no-num no-toc">Draft Standard — 30 November 2010</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -47481,6 +47481,20 @@
<li><p>Let <var title="">target</var> be the <var title="">submitter</var> element's <a href=#concept-fs-target title=concept-fs-target>target</a>.</li>
+ <li><p>If the user indicated a specific <a href=#browsing-context>browsing
+ context</a> to use when submitting the form, then let <var title="">target browsing context</var> be that <a href=#browsing-context>browsing
+ context</a>. Otherwise, apply <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 <var title="">target</var> as the name and the <a href=#browsing-context>browsing
+ context</a> of <var title="">form</var> as the context in which
+ the algorithm is executed, and let <var title="">target browsing
+ context</var> be the resulting <a href=#browsing-context>browsing
+ context</a>.</li>
+
+ <li><p>If <var title="">target browsing context</var> was created
+ in the previous step, then let <var title="">replace</var> be true.
+ Otherwise, let it be false.</li>
+ <!-- XXXXX this is about to change -->
+
<li>
<p>Select the appropriate row in the table below based on the
@@ -47535,14 +47549,11 @@
replaced by <var title="">query</var> (adding a U+003F QUESTION
MARK character (?) if appropriate).</p>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p><a href=#navigate>Navigate</a><!--DONAV form--> <var title="">target
browsing context</var> to <var title="">destination</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <a href=#replacement-enabled>replacement enabled</a>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href=#replacement-enabled>replacement
+ enabled</a>.</p>
</dd>
@@ -47553,9 +47564,6 @@
the <var title="">form data set</var> using the
<a href=#appropriate-form-encoding-algorithm>appropriate form encoding algorithm</a>.</p>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p>Let <var title="">MIME type</var> be determined as
follows:</p>
@@ -47579,22 +47587,19 @@
POST can trigger this now, and that's historically
unrestricted)--><p>Otherwise, <a href=#navigate>navigate</a><!--DONAV form--> <var title="">target browsing context</var> to <var title="">action</var> using the HTTP method given by <var title="">method</var> and with <var title="">entity body</var>
as the entity body, of type <var title="">MIME type</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <a href=#replacement-enabled>replacement enabled</a>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href=#replacement-enabled>replacement
+ enabled</a>.</p>
</dd>
<dt><dfn id=submit-get-action title=submit-get-action>Get action</dfn>
<dd>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p><a href=#navigate>Navigate</a><!--DONAV form--> <var title="">target
- browsing context</var> to <var title="">action</var>. If <var title="">target browsing context</var> was newly created for
- this purpose by the steps above, then it must be navigated with
- <a href=#replacement-enabled>replacement enabled</a>.</p>
+ browsing context</var> to <var title="">action</var>. If <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href=#replacement-enabled>replacement
+ enabled</a>.</p>
</dd>
@@ -47621,14 +47626,10 @@
string, replace the first occurrence of "<code title="">%%</code>" in <var title="">action</var> with the
resulting escaped string. <a href=#refsRFC3986>[RFC3986]</a></p>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p><a href=#navigate>Navigate</a><!--DONAV form--> <var title="">target
- browsing context</var> to the potentially modified <var title="">action</var>. If <var title="">target browsing
- context</var> was newly created for this purpose by the steps
- above, then it must be navigated with <a href=#replacement-enabled>replacement
- enabled</a>.</p>
+ browsing context</var> to the potentially modified <var title="">action</var>. If <var title="">replace</var> is true,
+ then <var title="">target browsing context</var> must be
+ navigated with <a href=#replacement-enabled>replacement enabled</a>.</p>
</dd>
@@ -47651,14 +47652,11 @@
<p>Append <var title="">headers</var> to <var title="">destination</var>.</p>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p><a href=#navigate>Navigate</a><!--DONAV form--> <var title="">target
browsing context</var> to <var title="">destination</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <a href=#replacement-enabled>replacement enabled</a>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href=#replacement-enabled>replacement
+ enabled</a>.</p>
</dd>
@@ -47685,29 +47683,15 @@
<p>Append <var title="">body</var>, interpreted as a US-ASCII
string, to <var title="">destination</var>.</p>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p><a href=#navigate>Navigate</a><!--DONAV form--> <var title="">target
browsing context</var> to <var title="">destination</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <a href=#replacement-enabled>replacement enabled</a>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href=#replacement-enabled>replacement
+ enabled</a>.</p>
</dd>
- </dl><p><dfn id=the-form-submission-target-browsing-context>The form submission target browsing context</dfn> is
- obtained, when needed by the behaviors described above, as
- follows: If the user indicated a specific <a href=#browsing-context>browsing
- context</a> to use when submitting the form, then that is the
- target browsing context. Otherwise, apply <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 <var title="">target</var> as the name and the
- <a href=#browsing-context>browsing context</a> of <var title="">form</var> as the
- context in which the algorithm is executed; the resulting
- <a href=#browsing-context>browsing context</a> is the target browsing context.</p>
-
- <p>The <dfn id=appropriate-form-encoding-algorithm>appropriate form encoding algorithm</dfn> is
+ </dl><p>The <dfn id=appropriate-form-encoding-algorithm>appropriate form encoding algorithm</dfn> is
determined as follows:</p>
<dl><dt>If <var title="">enctype</var> is <code title=attr-fs-enctype-urlencoded><a href=#attr-fs-enctype-urlencoded>application/x-www-form-urlencoded</a></code></dt>
@@ -58921,6 +58905,7 @@
must act as if the <code title=dom-location-assign><a href=#dom-location-assign>assign()</a></code>
method had been called with the new value as its argument.</p><!--
v2: may wish to allow replace instead as a UI improvement -->
+ <!-- XXXXX the above is about to change -->
<!-- we could change the magic .location setter to simply refer
straight to assign(), so we don't have two levels of indirection -->
Modified: index
===================================================================
--- index 2010-11-29 22:56:34 UTC (rev 5683)
+++ index 2010-11-30 00:41:19 UTC (rev 5684)
@@ -218,7 +218,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1>HTML5 (including next generation additions still in development)</h1>
- <h2 class="no-num no-toc">Draft Standard — 29 November 2010</h2>
+ <h2 class="no-num no-toc">Draft Standard — 30 November 2010</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -47461,6 +47461,20 @@
<li><p>Let <var title="">target</var> be the <var title="">submitter</var> element's <a href=#concept-fs-target title=concept-fs-target>target</a>.</li>
+ <li><p>If the user indicated a specific <a href=#browsing-context>browsing
+ context</a> to use when submitting the form, then let <var title="">target browsing context</var> be that <a href=#browsing-context>browsing
+ context</a>. Otherwise, apply <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 <var title="">target</var> as the name and the <a href=#browsing-context>browsing
+ context</a> of <var title="">form</var> as the context in which
+ the algorithm is executed, and let <var title="">target browsing
+ context</var> be the resulting <a href=#browsing-context>browsing
+ context</a>.</li>
+
+ <li><p>If <var title="">target browsing context</var> was created
+ in the previous step, then let <var title="">replace</var> be true.
+ Otherwise, let it be false.</li>
+ <!-- XXXXX this is about to change -->
+
<li>
<p>Select the appropriate row in the table below based on the
@@ -47515,14 +47529,11 @@
replaced by <var title="">query</var> (adding a U+003F QUESTION
MARK character (?) if appropriate).</p>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p><a href=#navigate>Navigate</a><!--DONAV form--> <var title="">target
browsing context</var> to <var title="">destination</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <a href=#replacement-enabled>replacement enabled</a>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href=#replacement-enabled>replacement
+ enabled</a>.</p>
</dd>
@@ -47533,9 +47544,6 @@
the <var title="">form data set</var> using the
<a href=#appropriate-form-encoding-algorithm>appropriate form encoding algorithm</a>.</p>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p>Let <var title="">MIME type</var> be determined as
follows:</p>
@@ -47559,22 +47567,19 @@
POST can trigger this now, and that's historically
unrestricted)--><p>Otherwise, <a href=#navigate>navigate</a><!--DONAV form--> <var title="">target browsing context</var> to <var title="">action</var> using the HTTP method given by <var title="">method</var> and with <var title="">entity body</var>
as the entity body, of type <var title="">MIME type</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <a href=#replacement-enabled>replacement enabled</a>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href=#replacement-enabled>replacement
+ enabled</a>.</p>
</dd>
<dt><dfn id=submit-get-action title=submit-get-action>Get action</dfn>
<dd>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p><a href=#navigate>Navigate</a><!--DONAV form--> <var title="">target
- browsing context</var> to <var title="">action</var>. If <var title="">target browsing context</var> was newly created for
- this purpose by the steps above, then it must be navigated with
- <a href=#replacement-enabled>replacement enabled</a>.</p>
+ browsing context</var> to <var title="">action</var>. If <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href=#replacement-enabled>replacement
+ enabled</a>.</p>
</dd>
@@ -47601,14 +47606,10 @@
string, replace the first occurrence of "<code title="">%%</code>" in <var title="">action</var> with the
resulting escaped string. <a href=#refsRFC3986>[RFC3986]</a></p>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p><a href=#navigate>Navigate</a><!--DONAV form--> <var title="">target
- browsing context</var> to the potentially modified <var title="">action</var>. If <var title="">target browsing
- context</var> was newly created for this purpose by the steps
- above, then it must be navigated with <a href=#replacement-enabled>replacement
- enabled</a>.</p>
+ browsing context</var> to the potentially modified <var title="">action</var>. If <var title="">replace</var> is true,
+ then <var title="">target browsing context</var> must be
+ navigated with <a href=#replacement-enabled>replacement enabled</a>.</p>
</dd>
@@ -47631,14 +47632,11 @@
<p>Append <var title="">headers</var> to <var title="">destination</var>.</p>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p><a href=#navigate>Navigate</a><!--DONAV form--> <var title="">target
browsing context</var> to <var title="">destination</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <a href=#replacement-enabled>replacement enabled</a>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href=#replacement-enabled>replacement
+ enabled</a>.</p>
</dd>
@@ -47665,29 +47663,15 @@
<p>Append <var title="">body</var>, interpreted as a US-ASCII
string, to <var title="">destination</var>.</p>
- <p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
- form submission target browsing context</a>.</p>
-
<p><a href=#navigate>Navigate</a><!--DONAV form--> <var title="">target
browsing context</var> to <var title="">destination</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <a href=#replacement-enabled>replacement enabled</a>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href=#replacement-enabled>replacement
+ enabled</a>.</p>
</dd>
- </dl><p><dfn id=the-form-submission-target-browsing-context>The form submission target browsing context</dfn> is
- obtained, when needed by the behaviors described above, as
- follows: If the user indicated a specific <a href=#browsing-context>browsing
- context</a> to use when submitting the form, then that is the
- target browsing context. Otherwise, apply <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 <var title="">target</var> as the name and the
- <a href=#browsing-context>browsing context</a> of <var title="">form</var> as the
- context in which the algorithm is executed; the resulting
- <a href=#browsing-context>browsing context</a> is the target browsing context.</p>
-
- <p>The <dfn id=appropriate-form-encoding-algorithm>appropriate form encoding algorithm</dfn> is
+ </dl><p>The <dfn id=appropriate-form-encoding-algorithm>appropriate form encoding algorithm</dfn> is
determined as follows:</p>
<dl><dt>If <var title="">enctype</var> is <code title=attr-fs-enctype-urlencoded><a href=#attr-fs-enctype-urlencoded>application/x-www-form-urlencoded</a></code></dt>
@@ -58901,6 +58885,7 @@
must act as if the <code title=dom-location-assign><a href=#dom-location-assign>assign()</a></code>
method had been called with the new value as its argument.</p><!--
v2: may wish to allow replace instead as a UI improvement -->
+ <!-- XXXXX the above is about to change -->
<!-- we could change the magic .location setter to simply refer
straight to assign(), so we don't have two levels of indirection -->
Modified: source
===================================================================
--- source 2010-11-29 22:56:34 UTC (rev 5683)
+++ source 2010-11-30 00:41:19 UTC (rev 5684)
@@ -53360,6 +53360,22 @@
title="">submitter</var> element's <span
title="concept-fs-target">target</span>.</p></li>
+ <li><p>If the user indicated a specific <span>browsing
+ context</span> to use when submitting the form, then let <var
+ title="">target browsing context</var> be that <span>browsing
+ context</span>. Otherwise, apply <span>the rules for choosing a
+ browsing context given a browsing context name</span> using <var
+ title="">target</var> as the name and the <span>browsing
+ context</span> of <var title="">form</var> as the context in which
+ the algorithm is executed, and let <var title="">target browsing
+ context</var> be the resulting <span>browsing
+ context</span>.</p></li>
+
+ <li><p>If <var title="">target browsing context</var> was created
+ in the previous step, then let <var title="">replace</var> be true.
+ Otherwise, let it be false.</p></li>
+ <!-- XXXXX this is about to change -->
+
<li>
<p>Select the appropriate row in the table below based on the
@@ -53429,14 +53445,11 @@
replaced by <var title="">query</var> (adding a U+003F QUESTION
MARK character (?) if appropriate).</p>
- <p>Let <var title="">target browsing context</var> be <span>the
- form submission target browsing context</span>.</p>
-
<p><span>Navigate</span><!--DONAV form--> <var title="">target
browsing context</var> to <var title="">destination</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <span>replacement enabled</span>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <span>replacement
+ enabled</span>.</p>
</dd>
@@ -53447,9 +53460,6 @@
the <var title="">form data set</var> using the
<span>appropriate form encoding algorithm</span>.</p>
- <p>Let <var title="">target browsing context</var> be <span>the
- form submission target browsing context</span>.</p>
-
<p>Let <var title="">MIME type</var> be determined as
follows:</p>
@@ -53484,23 +53494,20 @@
title="">action</var> using the HTTP method given by <var
title="">method</var> and with <var title="">entity body</var>
as the entity body, of type <var title="">MIME type</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <span>replacement enabled</span>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <span>replacement
+ enabled</span>.</p>
</dd>
<dt><dfn title="submit-get-action">Get action</dfn>
<dd>
- <p>Let <var title="">target browsing context</var> be <span>the
- form submission target browsing context</span>.</p>
-
<p><span>Navigate</span><!--DONAV form--> <var title="">target
browsing context</var> to <var title="">action</var>. If <var
- title="">target browsing context</var> was newly created for
- this purpose by the steps above, then it must be navigated with
- <span>replacement enabled</span>.</p>
+ title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <span>replacement
+ enabled</span>.</p>
</dd>
@@ -53534,15 +53541,11 @@
resulting escaped string. <a
href="#refsRFC3986">[RFC3986]</a></p>
- <p>Let <var title="">target browsing context</var> be <span>the
- form submission target browsing context</span>.</p>
-
<p><span>Navigate</span><!--DONAV form--> <var title="">target
browsing context</var> to the potentially modified <var
- title="">action</var>. If <var title="">target browsing
- context</var> was newly created for this purpose by the steps
- above, then it must be navigated with <span>replacement
- enabled</span>.</p>
+ title="">action</var>. If <var title="">replace</var> is true,
+ then <var title="">target browsing context</var> must be
+ navigated with <span>replacement enabled</span>.</p>
</dd>
@@ -53570,14 +53573,11 @@
<p>Append <var title="">headers</var> to <var
title="">destination</var>.</p>
- <p>Let <var title="">target browsing context</var> be <span>the
- form submission target browsing context</span>.</p>
-
<p><span>Navigate</span><!--DONAV form--> <var title="">target
browsing context</var> to <var title="">destination</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <span>replacement enabled</span>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <span>replacement
+ enabled</span>.</p>
</dd>
@@ -53606,30 +53606,16 @@
<p>Append <var title="">body</var>, interpreted as a US-ASCII
string, to <var title="">destination</var>.</p>
- <p>Let <var title="">target browsing context</var> be <span>the
- form submission target browsing context</span>.</p>
-
<p><span>Navigate</span><!--DONAV form--> <var title="">target
browsing context</var> to <var title="">destination</var>. If
- <var title="">target browsing context</var> was newly created
- for this purpose by the steps above, then it must be navigated
- with <span>replacement enabled</span>.</p>
+ <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <span>replacement
+ enabled</span>.</p>
</dd>
</dl>
- <p><dfn>The form submission target browsing context</dfn> is
- obtained, when needed by the behaviors described above, as
- follows: If the user indicated a specific <span>browsing
- context</span> to use when submitting the form, then that is the
- target browsing context. Otherwise, apply <span>the rules for
- choosing a browsing context given a browsing context name</span>
- using <var title="">target</var> as the name and the
- <span>browsing context</span> of <var title="">form</var> as the
- context in which the algorithm is executed; the resulting
- <span>browsing context</span> is the target browsing context.</p>
-
<p>The <dfn>appropriate form encoding algorithm</dfn> is
determined as follows:</p>
@@ -66935,6 +66921,7 @@
must act as if the <code title="dom-location-assign">assign()</code>
method had been called with the new value as its argument.</p><!--
v2: may wish to allow replace instead as a UI improvement -->
+ <!-- XXXXX the above is about to change -->
<!-- we could change the magic .location setter to simply refer
straight to assign(), so we don't have two levels of indirection -->
More information about the Commit-Watchers
mailing list