- From: poot <cvsmail@w3.org>
- Date: Tue, 30 Nov 2010 09:43:25 +0900 (JST)
- To: public-html-diffs@w3.org
hixie: Refactor form submission browsing context details. This in theory
didn't change anything. (whatwg r5684)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4551&r2=1.4552&f=h
http://html5.org/tools/web-apps-tracker?from=5683&to=5684
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4551
retrieving revision 1.4552
diff -u -d -r1.4551 -r1.4552
--- Overview.html 29 Nov 2010 22:56:46 -0000 1.4551
+++ Overview.html 30 Nov 2010 00:41:25 -0000 1.4552
@@ -38129,6 +38129,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
@@ -38183,14 +38197,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>
@@ -38201,9 +38212,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>
@@ -38227,22 +38235,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>
@@ -38269,14 +38274,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>
@@ -38299,14 +38300,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>
@@ -38333,29 +38331,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>
@@ -43675,6 +43659,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 -->
Received on Tuesday, 30 November 2010 00:43:55 UTC