- From: poot <cvsmail@w3.org>
- Date: Wed, 17 Jun 2009 16:12:29 +0900 (JST)
- To: public-html-diffs@w3.org
more cleanup (whatwg r3303)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2448&r2=1.2449&f=h
http://html5.org/tools/web-apps-tracker?from=3302&to=3303
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2448
retrieving revision 1.2449
diff -u -d -r1.2448 -r1.2449
--- Overview.html 17 Jun 2009 07:01:59 -0000 1.2448
+++ Overview.html 17 Jun 2009 07:12:12 -0000 1.2449
@@ -44413,7 +44413,7 @@
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>
@@ -45510,30 +45510,33 @@
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
@@ -46093,10 +46096,7 @@
<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=""><?xml-stylesheet?></code> and <code title=""><?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
@@ -46738,10 +46738,8 @@
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><!-- resolving ping urls happens at audit time, so base URL changes
affect the values of ping attributes --><h4 id="linkTypes"><span class="secno">6.12.3 </span>Link types</h4><p>The following table summarizes the link types that are defined by
@@ -46872,37 +46870,11 @@
specified by user agents, but<!--</span>--> must not be used in
documents.</p>
- </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.
-
- --><h5 id="link-type-alternate"><span class="secno">6.12.3.1 </span>Link type "<dfn title="rel-alternate"><code>alternate</code></dfn>"</h5><p>The <code title="rel-alternate"><a href="#link-type-alternate">alternate</a></code> keyword may be
+ </div><!-- 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><p>The <code title="rel-alternate"><a href="#link-type-alternate">alternate</a></code> keyword may be
used with <code><a href="#the-link-element">link</a></code>, <code><a href="#the-a-element">a</a></code>, and <code><a href="#the-area-element">area</a></code>
elements. For <code><a href="#the-link-element">link</a></code> elements, if the <code title="attr-link-rel"><a href="#attr-link-rel">rel</a></code> attribute does not also contain the
keyword <code title="rel-stylesheet"><a href="#link-type-stylesheet">stylesheet</a></code>, it creates a
@@ -47257,9 +47229,7 @@
the referenced document provides an interface specifically for
searching the document and its related resources.<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="#references">[OPENSEARCH]</a></p><!-- XXX
- http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML
- --><h5 id="link-type-stylesheet"><span class="secno">6.12.3.15 </span>Link type "<dfn title="rel-stylesheet"><code>stylesheet</code></dfn>"</h5><p>The <code title="rel-stylesheet"><a href="#link-type-stylesheet">stylesheet</a></code> keyword may be
+ autodiscover search interfaces. <a href="#references">[OPENSEARCH]</a><h5 id="link-type-stylesheet"><span class="secno">6.12.3.15 </span>Link type "<dfn title="rel-stylesheet"><code>stylesheet</code></dfn>"</h5><p>The <code title="rel-stylesheet"><a href="#link-type-stylesheet">stylesheet</a></code> keyword may be
used with <code><a href="#the-link-element">link</a></code> elements, for which it creates an <a href="#external-resource-link" title="external resource link">external resource link</a> that
contributes to the <a href="#styling">styling processing model</a>.<p>The specified resource is a resource that describes how to
present the document. Exactly how the resource is to be processed
@@ -47594,7 +47564,7 @@
<li><p>Set the <var title="">click in progress</var> flag on the
element to false.</li>
- </ol></div><h3 id="scrolling-elements-into-view"><span class="secno">7.4 </span>Scrolling elements into view</h3><dl class="domintro"><dt><var title="">element</var> . <code title="dom-scrollIntoView"><a href="#dom-scrollintoview">scrollIntoView</a></code>( [ <var title="">top</var> ] )</dt>
+ </ol></div><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>
<dd>
@@ -47631,8 +47601,6 @@
<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><h3 id="focus"><span class="secno">7.5 </span>Focus</h3><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%20%0A...%3Cform%3E%3Cinput%20name%3Da%20onfocus%3D%22value%2B%3D1%3Bd.name%3D%27a%27%3Bname%3D%27d%27%3Bb.focus()%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22value%2B%3D1%3Bc.focus()%22%3E%0A%3Cinput%20name%3Dc%20onfocus%3D%22value%2B%3D1%3Bd.focus()%22%3E%0A%3Cinput%20name%3Dd%20onfocus%3D%22value%2B%3D1%3Ba.focus()%22%3E --><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cform%3E%0A%3Ctextarea%20name%3Dt%20cols%3D100%20rows%3D3%3E%3C%2Ftextarea%3E%3Cp%3E%0A%3Cinput%20name%3Da%20onfocus%3D%22t.value%2B%3D%27af1%20%27%3Bb.focus()%3Balert(document.activeElement.name)%3Bt.value%2B%3D%27af2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27ab%20%27%3B%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22t.value%2B%3D%27bf1%20%27%3Bc.focus()%3Bt.value%2B%3D%27bf2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27bb%20%27%3B%22%3E%0A%3Cinput%20name%3Dc%2onfocus%3D%22t.value%2B%3D%27cf1%20%27%3Bc.focus()%3Bt.value%2B%3D%27cf2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27cb%20%27%3B%22%3E%0A --><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Cbody%20onload%3D%22document.forms%5B0%5D.a.focus()%22%3E%0A...%3Cform%3E%0A%3Ctextarea%20name%3Dt%20cols%3D100%20rows%3D3%3E%3C%2Ftextarea%3E%3Cp%3E%0A%3Cinput%20name%3Da%20onblur%3D%22t.value%2B%3D'ab%20'%3B%20b.focus()%3B%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22t.value%2B%3D'bf1%20'%3Ba.focus()%3Bt.value%2B%3D'bf2%20'%3B%22%20onblur%3D%22t.value%2B%3D'bb%20'%3B%22%3E --><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Cbody%3E...%3Cform%3E%0A%3Ctextarea%20name%3Dt%20cols%3D100%20rows%3D3%3E%3C%2Ftextarea%3E%3Cp%3E%0A%3Cinput%20name%3Da%20onfocus%3D%22t.value%2B%3D%27af%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27ab1%20%27%3Bb.focus()%3Bt.value%2B%3D%27ab2%20%27%3B%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22t.value%2B%3D%27bf1%20%27%3Ba.focus()%3Bt.valu%2B%3D%27bf2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27bb%20%27%3B%22%3E --><!-- XXX
- define onfocus/onblur behaviour for Window
- Other things to look at are IE's focus APIs (HTMLElement.setActive(),
@@ -63809,6 +63777,7 @@
[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]
Received on Wednesday, 17 June 2009 07:13:03 UTC