[html5] r3350 - [] (0) Mark impl-specific mirodata sections as such. Make some non-normative tex [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Jul 1 14:38:48 PDT 2009
Author: ianh
Date: 2009-07-01 14:38:46 -0700 (Wed, 01 Jul 2009)
New Revision: 3350
Modified:
index
source
Log:
[] (0) Mark impl-specific mirodata sections as such. Make some non-normative text more obviously non-normative. Make location.assign() act like .replace() when performed on the initial about:blank document. Fix markup error.
Modified: index
===================================================================
--- index 2009-07-01 04:44:24 UTC (rev 3349)
+++ index 2009-07-01 21:38:46 UTC (rev 3350)
@@ -43751,6 +43751,7 @@
+ <div class=impl>
<h3 id=converting-html-to-other-formats><span class=secno>5.5 </span>Converting HTML to other formats</h3>
@@ -45326,6 +45327,7 @@
</ol><p>The <dfn id=atom-namespace>Atom namespace</dfn> is: <code>http://www.w3.org/2005/Atom</code></p>
+ </div>
@@ -45438,8 +45440,10 @@
<code><a href=#about:blank>about:blank</a></code>, which is marked as being an <a href=#html-documents title="HTML documents">HTML document</a>, and whose <a href="#document's-character-encoding" title="document's character encoding">character encoding</a> is
UTF-8. The <code>Document</code> must have a single child
<code><a href=#the-html-element>html</a></code> node, which itself has a single child
- <code><a href=#the-body-element>body</a></code> node. If the <a href=#browsing-context>browsing context</a> is
- created specifically to be immediately navigated, then that initial
+ <code><a href=#the-body-element>body</a></code> node.</p>
+
+ <p class=note>If the <a href=#browsing-context>browsing context</a> is created
+ specifically to be immediately navigated, then that initial
navigation will have <a href=#replacement-enabled>replacement enabled</a>.</p>
<p id=about-blank-origin>The <a href=#origin-0>origin</a> of the
@@ -45751,7 +45755,7 @@
the <a href=#sandboxed-navigation-browsing-context-flag>sandboxed navigation browsing context flag</a>
set.</dt>
- <dd>The user agent may offer to create a new <a href=#top-level-browsing-context>top-level
+ <dd><p>The user agent may offer to create a new <a href=#top-level-browsing-context>top-level
browsing context</a> or reuse an existing <a href=#top-level-browsing-context>top-level
browsing context</a>. If the user picks one of those options,
then the designated browsing context must be the chosen one (the
@@ -45765,35 +45769,40 @@
browsing context is being requested as part of <a href=#following-hyperlinks title="following hyperlinks">following a hyperlink</a> whose
<a href=#linkTypes>link types</a> include the <code title=rel-noreferrer><a href=#link-type-noreferrer>noreferrer</a></code> keyword</dt>
- <dd>A new <a href=#top-level-browsing-context>top-level browsing context</a> must be
+ <dd><p>A new <a href=#top-level-browsing-context>top-level browsing context</a> must be
created. If the given browsing context name is not <code title="">_blank</code>, then the new top-level browsing context's
name must be the given browsing context name (otherwise, it has
no name). The chosen browsing context must be this new browsing
- context. If it is immediately <a href=#navigate title=navigate>navigated</a>, then the navigation will be
+ context.</p>
+
+ <p class=note>If it is immediately <a href=#navigate title=navigate>navigated</a>, then the navigation will be
done with <a href=#replacement-enabled>replacement enabled</a>.</dd>
<dt>If the user agent has been configured such that in this
instance it will create a new browsing context, and the <code title=rel-noreferrer><a href=#link-type-noreferrer>noreferrer</a></code> keyword doesn't
apply</dt>
- <dd>A new <a href=#auxiliary-browsing-context>auxiliary browsing context</a> must be
+ <dd><p>A new <a href=#auxiliary-browsing-context>auxiliary browsing context</a> must be
created, with the <a href=#opener-browsing-context>opener browsing context</a> being the
current one. If the given browsing context name is not <code title="">_blank</code>, then the new auxiliary browsing context's
name must be the given browsing context name (otherwise, it has
no name). The chosen browsing context must be this new browsing
- context. If it is immediately <a href=#navigate title=navigate>navigated</a>, then the navigation will be
- done with <a href=#replacement-enabled>replacement enabled</a>.</dd>
+ context.</p>
+ <p>If it is immediately <a href=#navigate title=navigate>navigated</a>,
+ then the navigation will be done with <a href=#replacement-enabled>replacement
+ enabled</a>.</dd>
+
<dt>If the user agent has been configured such that in this
instance it will reuse the current browsing context</dt>
- <dd>The chosen browsing context is the current browsing
+ <dd><p>The chosen browsing context is the current browsing
context.</dd>
<dt>If the user agent has been configured such that in this
instance it will not find a browsing context</dt>
- <dd>There must not be a chosen browsing context.</dd>
+ <dd><p>There must not be a chosen browsing context.</dd>
</dl><p>User agent implementors are encouraged to provide a way for
users to configure the user agent to always reuse the current
@@ -51331,12 +51340,15 @@
<a href=#resolve-a-url title="resolve a url">resolve</a> the argument, relative to
the <a href=#first-script>first script</a>'s <a href="#script's-base-url" title="script's base URL">base
URL</a>, and if that is successful, must <a href=#navigate>navigate</a>
- the <a href=#browsing-context>browsing context</a> to the specified <var title="">url</var>.</p> <!-- READ ME WHEN EDITING THIS: browsers
- seem to treat this as having <span>replacement enabled</span> if the
- browsing context has only one entry and that entry is
- about:blank. IE and Firefox only seem to treat it that way if the
- DOM is still a virgin DOM; Safari doesn't check that. Thus this
- might need changing if testing shows their behaviour is required
+ the <a href=#browsing-context>browsing context</a> to the specified <var title="">url</var>. If the <a href=#browsing-context>browsing context</a>'s
+ <a href=#session-history>session history</a> contains only one
+ <code>Document</code>, and that was the <code><a href=#about:blank>about:blank</a></code>
+ <code>Document</code> created when the <a href=#browsing-context>browsing context</a>
+ was created, then the navigation must be done with
+ <a href=#replacement-enabled>replacement enabled</a>.</p> <!-- READ ME WHEN EDITING
+ THIS: IE and Firefox only seem to treat it that way if the DOM is
+ still a virgin DOM; Safari doesn't check that. Thus this might need
+ changing if testing shows the IE/Firefox behaviour is required
here. -->
<p>When the <dfn id=dom-location-replace title=dom-location-replace><code>replace(<var title="">url</var>)</code></dfn> method is invoked, the UA must
@@ -55869,10 +55881,10 @@
and <a href=#extracting-json title="extracting JSON">extract the microdata from those
nodes into a JSON form</a>, and then must add the resulting
string to the <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code> member,
- associated with the <code title="">application/microdata+json</code> format.</li> <!-- XXX
+ associated with the <code title="">application/microdata+json</code> format.</p> <!-- XXX
register -->
- <li>
+ </li>
<li>
Modified: source
===================================================================
--- source 2009-07-01 04:44:24 UTC (rev 3349)
+++ source 2009-07-01 21:38:46 UTC (rev 3350)
@@ -49447,6 +49447,7 @@
+ <div class="impl">
<h3>Converting HTML to other formats</h3>
@@ -51611,6 +51612,7 @@
<p>The <dfn>Atom namespace</dfn> is: <code>http://www.w3.org/2005/Atom</code></p>
+ </div>
@@ -51733,8 +51735,10 @@
title="document's character encoding">character encoding</span> is
UTF-8. The <code>Document</code> must have a single child
<code>html</code> node, which itself has a single child
- <code>body</code> node. If the <span>browsing context</span> is
- created specifically to be immediately navigated, then that initial
+ <code>body</code> node.</p>
+
+ <p class="note">If the <span>browsing context</span> is created
+ specifically to be immediately navigated, then that initial
navigation will have <span>replacement enabled</span>.</p>
<p id="about-blank-origin">The <span>origin</span> of the
@@ -52085,14 +52089,14 @@
the <span>sandboxed navigation browsing context flag</span>
set.</dt>
- <dd>The user agent may offer to create a new <span>top-level
+ <dd><p>The user agent may offer to create a new <span>top-level
browsing context</span> or reuse an existing <span>top-level
browsing context</span>. If the user picks one of those options,
then the designated browsing context must be the chosen one (the
browsing context's name isn't set to the given browsing context
name). Otherwise (if the user agent doesn't offer the option to
the user, or if the user declines to allow a browsing context to
- be used) there must not be a chosen browsing context.</dd>
+ be used) there must not be a chosen browsing context.</p></dd>
<dt id="noopener">If the user agent has been configured such that
in this instance it will create a new browsing context, and the
@@ -52101,40 +52105,44 @@
<a href="#linkTypes">link types</a> include the <code
title="rel-noreferrer">noreferrer</code> keyword</dt>
- <dd>A new <span>top-level browsing context</span> must be
+ <dd><p>A new <span>top-level browsing context</span> must be
created. If the given browsing context name is not <code
title="">_blank</code>, then the new top-level browsing context's
name must be the given browsing context name (otherwise, it has
no name). The chosen browsing context must be this new browsing
- context. If it is immediately <span
+ context.</p>
+
+ <p class="note">If it is immediately <span
title="navigate">navigated</span>, then the navigation will be
- done with <span>replacement enabled</span>.</dd>
+ done with <span>replacement enabled</span>.</p></dd>
<dt>If the user agent has been configured such that in this
instance it will create a new browsing context, and the <code
title="rel-noreferrer">noreferrer</code> keyword doesn't
apply</dt>
- <dd>A new <span>auxiliary browsing context</span> must be
+ <dd><p>A new <span>auxiliary browsing context</span> must be
created, with the <span>opener browsing context</span> being the
current one. If the given browsing context name is not <code
title="">_blank</code>, then the new auxiliary browsing context's
name must be the given browsing context name (otherwise, it has
no name). The chosen browsing context must be this new browsing
- context. If it is immediately <span
- title="navigate">navigated</span>, then the navigation will be
- done with <span>replacement enabled</span>.</dd>
+ context.</p>
+ <p>If it is immediately <span title="navigate">navigated</span>,
+ then the navigation will be done with <span>replacement
+ enabled</span>.</p></dd>
+
<dt>If the user agent has been configured such that in this
instance it will reuse the current browsing context</dt>
- <dd>The chosen browsing context is the current browsing
- context.</dd>
+ <dd><p>The chosen browsing context is the current browsing
+ context.</p></dd>
<dt>If the user agent has been configured such that in this
instance it will not find a browsing context</dt>
- <dd>There must not be a chosen browsing context.</dd>
+ <dd><p>There must not be a chosen browsing context.</p></dd>
</dl>
@@ -58550,12 +58558,15 @@
the <span>first script</span>'s <span title="script's base URL">base
URL</span>, and if that is successful, must <span>navigate</span>
the <span>browsing context</span> to the specified <var
- title="">url</var>.</p> <!-- READ ME WHEN EDITING THIS: browsers
- seem to treat this as having <span>replacement enabled</span> if the
- browsing context has only one entry and that entry is
- about:blank. IE and Firefox only seem to treat it that way if the
- DOM is still a virgin DOM; Safari doesn't check that. Thus this
- might need changing if testing shows their behaviour is required
+ title="">url</var>. If the <span>browsing context</span>'s
+ <span>session history</span> contains only one
+ <code>Document</code>, and that was the <code>about:blank</code>
+ <code>Document</code> created when the <span>browsing context</span>
+ was created, then the navigation must be done with
+ <span>replacement enabled</span>.</p> <!-- READ ME WHEN EDITING
+ THIS: IE and Firefox only seem to treat it that way if the DOM is
+ still a virgin DOM; Safari doesn't check that. Thus this might need
+ changing if testing shows the IE/Firefox behaviour is required
here. -->
<p>When the <dfn title="dom-location-replace"><code>replace(<var
@@ -65483,10 +65494,10 @@
string to the <code
title="dom-DragEvent-dataTransfer">dataTransfer</code> member,
associated with the <code
- title="">application/microdata+json</code> format.</li> <!-- XXX
+ title="">application/microdata+json</code> format.</p> <!-- XXX
register -->
- <li>
+ </li>
<li>
More information about the Commit-Watchers
mailing list