Skip to content

Commit

Permalink
[e] (0) more cleanup
Browse files Browse the repository at this point in the history 
git-svn-id: http://svn.whatwg.org/webapps@3303 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Jun 17, 2009
1 parent 73bca69 commit 29f339c
Show file tree
Hide file tree
Showing 2 changed files with 68 additions and 133 deletions.
100 changes: 34 additions & 66 deletions index
View file
Expand Up @@ -49454,7 +49454,7 @@ style/default.css</pre>
display of some sort of user interface indicating to the user
that a file is being downloaded in preparation for updating the
application.</li> <!-- XXX need to include progress
information -->
information once progress spec is stable -->

<li>

Expand Down Expand Up @@ -50641,30 +50641,33 @@ style/default.css</pre>
address">the current address</a> of the associated
<code>Document</code> object, as an <a href=#absolute-url>absolute URL</a>.</p>

<p>On setting, <!--XXX Mozilla does this, but IE doesn't. What
should we do?: the behavior depends on the context in which the
script that set the attribute is running. If the script ran as the
direct result of the execution of a <code>script</code> element in
the document represented by the <code>Location</code> object's
associated <code>Document</code> object, then the user agent must
act as if the <code title="dom-location-replace">replace()</code>
method had been called with the new value as its
argument. Otherwise,--> the user agent 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><!-- XXX may wish to allow
replace instead as a UI improvement --> <!-- XXX if we decide to
make .href setters just be the same as calling assign(), then change
the magic location setter above simply refer straight to assign() as
well, so we don't have two levels of indirection -->
<p>On setting, <!-- READ ME WHEN EDITING THIS: Mozilla does this,
but IE doesn't. What should we do?: the behavior depends on the
context in which the script that set the attribute is running. If
the script ran as the direct result of the execution of a
<code>script</code> element in the document represented by the
<code>Location</code> object's associated <code>Document</code>
object, then the user agent must act as if the <code
title="dom-location-replace">replace()</code> method had been called
with the new value as its argument. Otherwise,--> the user agent
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 -->

<!-- we could change the magic .location setter to simply refer
straight to assign(), so we don't have two levels of indirection -->

<p>When the <dfn id=dom-location-assign title=dom-location-assign><code>assign(<var title="">url</var>)</code></dfn> method is invoked, the UA must
<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> <!-- XXX 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. -->
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
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
<a href=#resolve-a-url title="resolve a url">resolve</a> the argument, relative to
Expand Down Expand Up @@ -51239,10 +51242,7 @@ style/default.css</pre>
<p class=note>Because the processing of the <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute happens
only once the root element is parsed, any URLs referenced by
processing instructions before the root element (such as <code title="">&lt;?xml-stylesheet?&gt;</code> and <code title="">&lt;?xbl?&gt;</code> PIs) will be fetched from the network and
cannot be cached.</p> <!-- XXX any ideas for avoiding this, that
aren't a PI themselves? We can't delay the processing, since the
whole point of the <?xbl?> PI is to have the XBL sheet loaded before
the root element... -->
cannot be cached.</p><!-- v2: fix this somehow -->

<p>User agents may examine the namespace of the root
<code>Element</code> node of this <code>Document</code> object to
Expand Down Expand Up @@ -51927,10 +51927,8 @@ style/default.css</pre>
bandwidth so that the target page loads faster.</li>

</ul><p>Thus, while it is possible to track users without this feature,
authors are encouraged to use the <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute so that the user agent
can improve <!-- XXX optimize? --> the user experience.</p> <!--
XXX need a better way to end that sentence. It's what I mean, but
it sounds kooky. -->
authors are encouraged to use the <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute so that the user
agent can make the user experience more transparent.</p>

</div>

Expand Down Expand Up @@ -52083,38 +52081,11 @@ style/default.css</pre>

</div>


<!--XXX

issues for rel="", etc:
rel="alternate stylesheet"
rel="script"
rel="related" // see also
which relationship combinations are allowed
what multiple values might mean (multiple <a rel="top"> in the same document)
http://www.euronet.nl/~tekelenb/WWW/LINK/
http://shift.freezope.org/konq_rellinks/development_html
http://hixie.ch/specs/html/link/001
http://hixie.ch/specs/html/link/002
http://www.hixie.ch/specs/html/metadata
what UAs are supposed to do with this
do something about http://microformats.org/wiki/rel-enclosure

mpt says:
> "As with <a> elements, when <link> elements that use these relationships
> are present, UAs should render them. As with <a> elements, when <link>
> elements that use these relationships do not exist, UAs should not
> render them. UAs should not make <link> rendering any easier to hide
> than <a> rendering."

for microformats (e.g. to refer to an hcard from an hcalendar):
rel=xref
<a> and <area> only
The href attribute's value must start with a '#' character.
Indicates an in-page cross-reference. For the purposes of data mining tools, the subtree rooted
at the first element with the given ID must be treated as if it was cloned and replaced the <a> element.

-->
<!-- v2 ideas:
* rel="script"
* rel="related" // see also
* http://microformats.org/wiki/rel-enclosure
-->


<h5 id=link-type-alternate><span class=secno>6.12.3.1 </span>Link type "<dfn title=rel-alternate><code>alternate</code></dfn>"</h5>
Expand Down Expand Up @@ -52639,9 +52610,7 @@ at the first element with the given ID must be treated as if it was cloned and r

<p class=note>OpenSearch description documents can be used with
<code><a href=#the-link-element>link</a></code> elements and the <code title=rel-search><a href=#link-type-search>search</a></code> link type to enable user agents to
autodiscover search interfaces. <a href=#refsOPENSEARCH>[OPENSEARCH]</a></p> <!-- XXX
http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML
-->
autodiscover search interfaces. <a href=#refsOPENSEARCH>[OPENSEARCH]</a></p>


<h5 id=link-type-stylesheet><span class=secno>6.12.3.15 </span>Link type "<dfn title=rel-stylesheet><code>stylesheet</code></dfn>"</h5>
Expand Down Expand Up @@ -53135,7 +53104,7 @@ at the first element with the given ID must be treated as if it was cloned and r
</ol></div>


<h3 id=scrolling-elements-into-view><span class=secno>7.4 </span>Scrolling elements into view</h3>
<h3 id=scrolling-elements-into-view><span class=secno>7.4 </span>Scrolling elements into view</h3> <!-- maybe this should move to [CSSOM] -->

<dl class=domintro><dt><var title="">element</var> . <code title=dom-scrollIntoView><a href=#dom-scrollintoview>scrollIntoView</a></code>( [ <var title="">top</var> ] )</dt>

Expand Down Expand Up @@ -53174,8 +53143,6 @@ at the first element with the given ID must be treated as if it was cloned and r
<p>Non-visual user agents may ignore the argument, or may treat it
in some media-specific manner most useful to the user.</p>

<!-- XXX maybe this should move to CSSOM -->

</div>


Expand Down Expand Up @@ -70048,6 +70015,7 @@ time:empty { binding: <i title="">time</i>; }</pre>
[IANACHARSET] http://www.iana.org/assignments/character-sets
[ISO885911] http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=28263
[MIMESNIFF] http://tools.ietf.org/html/draft-abarth-mime-sniff
[OPENSEARCH] http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML
[RFC1345] Simonsen, K., "Character Mnemonics & Character Sets", RFC 1345, Rationel Almen Planlaegning, Rationel Almen Planlaegning, June 1992.
[SCSU] http://www.unicode.org/unicode/reports/tr6/
[SELECTORS]
Expand Down
101 changes: 34 additions & 67 deletions source
View file
Expand Up @@ -56377,7 +56377,7 @@ style/default.css</pre>
display of some sort of user interface indicating to the user
that a file is being downloaded in preparation for updating the
application.</p></li> <!-- XXX need to include progress
information -->
information once progress spec is stable -->

<li>

Expand Down Expand Up @@ -57759,33 +57759,35 @@ style/default.css</pre>
address">the current address</span> of the associated
<code>Document</code> object, as an <span>absolute URL</span>.</p>

<p>On setting, <!--XXX Mozilla does this, but IE doesn't. What
should we do?: the behavior depends on the context in which the
script that set the attribute is running. If the script ran as the
direct result of the execution of a <code>script</code> element in
the document represented by the <code>Location</code> object's
associated <code>Document</code> object, then the user agent must
act as if the <code title="dom-location-replace">replace()</code>
method had been called with the new value as its
argument. Otherwise,--> the user agent must act as if the <code
title="dom-location-assign">assign()</code> method had been called
with the new value as its argument.</p><!-- XXX may wish to allow
replace instead as a UI improvement --> <!-- XXX if we decide to
make .href setters just be the same as calling assign(), then change
the magic location setter above simply refer straight to assign() as
well, so we don't have two levels of indirection -->
<p>On setting, <!-- READ ME WHEN EDITING THIS: Mozilla does this,
but IE doesn't. What should we do?: the behavior depends on the
context in which the script that set the attribute is running. If
the script ran as the direct result of the execution of a
<code>script</code> element in the document represented by the
<code>Location</code> object's associated <code>Document</code>
object, then the user agent must act as if the <code
title="dom-location-replace">replace()</code> method had been called
with the new value as its argument. Otherwise,--> the user agent
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 -->

<!-- we could change the magic .location setter to simply refer
straight to assign(), so we don't have two levels of indirection -->

<p>When the <dfn title="dom-location-assign"><code>assign(<var
title="">url</var>)</code></dfn> method is invoked, the UA must
<span title="resolve a url">resolve</span> the argument, relative to
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> <!-- XXX 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. -->
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
here. -->

<p>When the <dfn title="dom-location-replace"><code>replace(<var
title="">url</var>)</code></dfn> method is invoked, the UA must
Expand Down Expand Up @@ -58467,10 +58469,7 @@ style/default.css</pre>
processing instructions before the root element (such as <code
title="">&lt;?xml-stylesheet?></code> and <code
title="">&lt;?xbl?></code> PIs) will be fetched from the network and
cannot be cached.</p> <!-- XXX any ideas for avoiding this, that
aren't a PI themselves? We can't delay the processing, since the
whole point of the <?xbl?> PI is to have the XBL sheet loaded before
the root element... -->
cannot be cached.</p><!-- v2: fix this somehow -->

<p>User agents may examine the namespace of the root
<code>Element</code> node of this <code>Document</code> object to
Expand Down Expand Up @@ -60870,10 +60869,8 @@ interface <dfn>SQLTransactionSync</dfn> {

<p>Thus, while it is possible to track users without this feature,
authors are encouraged to use the <code
title="attr-hyperlink-ping">ping</code> attribute so that the user agent
can improve <!-- XXX optimize? --> the user experience.</p> <!--
XXX need a better way to end that sentence. It's what I mean, but
it sounds kooky. -->
title="attr-hyperlink-ping">ping</code> attribute so that the user
agent can make the user experience more transparent.</p>

</div>

Expand Down Expand Up @@ -61108,38 +61105,11 @@ interface <dfn>SQLTransactionSync</dfn> {

</div>


<!--XXX

issues for rel="", etc:
rel="alternate stylesheet"
rel="script"
rel="related" // see also
which relationship combinations are allowed
what multiple values might mean (multiple <a rel="top"> in the same document)
http://www.euronet.nl/~tekelenb/WWW/LINK/
http://shift.freezope.org/konq_rellinks/development_html
http://hixie.ch/specs/html/link/001
http://hixie.ch/specs/html/link/002
http://www.hixie.ch/specs/html/metadata
what UAs are supposed to do with this
do something about http://microformats.org/wiki/rel-enclosure

mpt says:
> "As with <a> elements, when <link> elements that use these relationships
> are present, UAs should render them. As with <a> elements, when <link>
> elements that use these relationships do not exist, UAs should not
> render them. UAs should not make <link> rendering any easier to hide
> than <a> rendering."

for microformats (e.g. to refer to an hcard from an hcalendar):
rel=xref
<a> and <area> only
The href attribute's value must start with a '#' character.
Indicates an in-page cross-reference. For the purposes of data mining tools, the subtree rooted
at the first element with the given ID must be treated as if it was cloned and replaced the <a> element.

-->
<!-- v2 ideas:
* rel="script"
* rel="related" // see also
* http://microformats.org/wiki/rel-enclosure
-->


<h5>Link type "<dfn title="rel-alternate"><code>alternate</code></dfn>"</h5>
Expand Down Expand Up @@ -61710,9 +61680,7 @@ at the first element with the given ID must be treated as if it was cloned and r
<code>link</code> elements and the <code
title="rel-search">search</code> link type to enable user agents to
autodiscover search interfaces. <a
href="#refsOPENSEARCH">[OPENSEARCH]</a></p> <!-- XXX
http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML
-->
href="#refsOPENSEARCH">[OPENSEARCH]</a></p>


<h5>Link type "<dfn title="rel-stylesheet"><code>stylesheet</code></dfn>"</h5>
Expand Down Expand Up @@ -62256,7 +62224,7 @@ at the first element with the given ID must be treated as if it was cloned and r
</div>


<h3>Scrolling elements into view</h3>
<h3>Scrolling elements into view</h3> <!-- maybe this should move to [CSSOM] -->

<dl class="domintro">

Expand Down Expand Up @@ -62300,8 +62268,6 @@ at the first element with the given ID must be treated as if it was cloned and r
<p>Non-visual user agents may ignore the argument, or may treat it
in some media-specific manner most useful to the user.</p>

<!-- XXX maybe this should move to CSSOM -->

</div>


Expand Down Expand Up @@ -82621,6 +82587,7 @@ time:empty { binding: <i title="">time</i>; }</pre>
[IANACHARSET] http://www.iana.org/assignments/character-sets
[ISO885911] http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=28263
[MIMESNIFF] http://tools.ietf.org/html/draft-abarth-mime-sniff
[OPENSEARCH] http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML
[RFC1345] Simonsen, K., "Character Mnemonics & Character Sets", RFC 1345, Rationel Almen Planlaegning, Rationel Almen Planlaegning, June 1992.
[SCSU] http://www.unicode.org/unicode/reports/tr6/
[SELECTORS]
Expand Down

0 comments on commit 29f339c

Please sign in to comment.