W3C home > Mailing lists > Public > public-html-commits@w3.org > June 2009

html5/spec Overview.html,1.2397,1.2398

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 15 Jun 2009 01:10:23 +0000
To: public-html-commits@w3.org
Message-Id: <E1MG0iN-0005Ku-GD@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv20498

Modified Files:
	Overview.html 
Log Message:
make some notes of v2 suggestions. (whatwg r3250)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2397
retrieving revision 1.2398
diff -u -d -r1.2397 -r1.2398
--- Overview.html	15 Jun 2009 00:42:40 -0000	1.2397
+++ Overview.html	15 Jun 2009 01:10:20 -0000	1.2398
@@ -4649,7 +4649,10 @@
 
   </div><h5 id="htmlcollection"><span class="secno">2.8.2.1 </span>HTMLCollection</h5><p>The <code><a href="#htmlcollection-0">HTMLCollection</a></code> interface represents a generic
   <a href="#collections-0" title="collections">collection</a> of elements.</p><!-- IE does [Callable] with magic that calls item() or namedItem() as appropriate as if it were a regular [[Get]],
-       so we might need to change this for compat. However, WebIDL doesn't support that for now. --><pre class="idl">[Callable=<a href="#dom-htmlcollection-nameditem" title="dom-HTMLCollection-namedItem">namedItem</a>]
+       so we might need to change this for compat. However, WebIDL doesn't support that for now. --><!-- heycam says we could just say something like "In the ECMAScript binding, host objects that implement interface
+       <code>HTMLCollection</code> have a [[Call]] method that that behaves as follows: 1. If called with 0 or more than 1
+       argument, throw a TypeError. 2. Let arg be the single argument passed. 3. Invoke [[Get]] on the object with ToString(argument)
+       as the property name. 4. Return Result(3)." (but we'd have to verify that that's right for 0 and >1 args) --><pre class="idl">[Callable=<a href="#dom-htmlcollection-nameditem" title="dom-HTMLCollection-namedItem">namedItem</a>]
 interface <dfn id="htmlcollection-0">HTMLCollection</dfn> {
   readonly attribute unsigned long <a href="#dom-htmlcollection-length" title="dom-HTMLCollection-length">length</a>;
   [IndexGetter] Element <a href="#dom-htmlcollection-item" title="dom-HTMLCollection-item">item</a>(in unsigned long index);
@@ -14182,7 +14185,22 @@
   readonly attribute boolean <a href="#dom-img-complete" title="dom-img-complete">complete</a>;
 };</pre>
    </dd>
-  </dl><p>An <code><a href="#the-img-element">img</a></code> element represents an image.<p>The image given by the <dfn id="attr-img-src" title="attr-img-src"><code>src</code></dfn> attribute is the
+  </dl><p>An <code><a href="#the-img-element">img</a></code> element represents an image.</p><!-- v2 ideas for <img>:
+
+     * Maps sites would like to know which images are already cached,
+       so that they can use images that are vaguely suitable while
+       they wait for the most appropriate image to download.
+
+       Almost like lowsrc="", except that many images might be
+       appropriate.
+
+       Slight hitch: their images are at a different origin, and we
+       don't want to allow arbitrary cross-origin inspection (privacy
+       leak risk).
+
+     * See note at rel=noreferrer.
+
+  --><p>The image given by the <dfn id="attr-img-src" title="attr-img-src"><code>src</code></dfn> attribute is the
   embedded content, and the value of the <dfn id="attr-img-alt" title="attr-img-alt"><code>alt</code></dfn> attribute is the
   <code><a href="#the-img-element">img</a></code> element's <a href="#fallback-content">fallback content</a>.<p>The <code title="attr-img-src"><a href="#attr-img-src">src</a></code> attribute must be
   present, and must contain a <a href="#valid-url">valid URL</a> referencing a
@@ -15353,7 +15371,30 @@
     Object specification. <a href="#references">[WINDOW]</a></p> <!--
     XXX -->
    </dd>
-  </dl><p>The <code><a href="#the-iframe-element">iframe</a></code> element <a href="#represents">represents</a> a
+  </dl><!-- v2 doc="" idea (awaiting implementation experience with seamless="" first):
+
+       http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2008-May/014874.html
+
+       doc="" would take a string which would then be interpreted as
+       the source document markup of an HTML document, much like the
+       above; it would override src="" if it was present, allowing
+       src="" to be used for legacy UAs:
+
+          <iframe seamless sandbox="allow-scripts allow-forms" doc="
+            <!DOCTYPE HTML>
+            <title></title>
+            Welcome to my blog!
+            </sandbox>
+            <a href='#' onclick='alert(document.cookie)'>Click here</a>
+          "></iframe>
+
+       (There are things we can do to make this better, e.g. make the
+       <!DOCTYPE HMTL> and <title></title> bits implicit, maybe
+       introducing type="" to say whether it's HTML or XML instead of
+       only supporting HTML, maybe saying that if src="" and doc=""
+       are both specified they must have identical data, etc.)
+
+  --><p>The <code><a href="#the-iframe-element">iframe</a></code> element <a href="#represents">represents</a> a
   <a href="#nested-browsing-context">nested browsing context</a>.<p>The <dfn id="attr-iframe-src" title="attr-iframe-src"><code>src</code></dfn> attribute
   gives the address of a page that the <a href="#nested-browsing-context">nested browsing
   context</a> is to contain. The attribute, if present, must be a
@@ -43560,7 +43601,16 @@
    called, release the <a href="#storage-mutex">storage mutex</a> so that it is once
    again free. Otherwise, it must do nothing.</p>
 
-  </div><h3 id="offline"><span class="secno">6.9 </span>Offline Web applications</h3><h4 id="introduction-4"><span class="secno">6.9.1 </span>Introduction</h4><p><em>This section is non-normative.</em><p class="XXX">...<div class="impl">
+  </div><h3 id="offline"><span class="secno">6.9 </span>Offline Web applications</h3><!-- v2 ideas for appcache:
+
+     * A way to limit what gets download when the user agent is
+       updating the application cache and it turns out the server has
+       changed EVERY page because every page has a dynamic "site last
+       modified" date on it.
+
+       http://groups.google.com/group/gears-users/browse_thread/thread/efbd808325df607a/c73adb34f9b63cf7?hl=en&q=whatwg#c73adb34f9b63cf7
+
+  --><h4 id="introduction-4"><span class="secno">6.9.1 </span>Introduction</h4><p><em>This section is non-normative.</em><p class="XXX">...<div class="impl">
 
   <h4 id="appcache"><span class="secno">6.9.2 </span>Application caches</h4>
 
@@ -47203,7 +47253,8 @@
   <p>This keyword also <a href="#noopener">causes the <code title="dom-opener">opener</code> attribute to remain null</a> if the
   hyperlink creates a new <a href="#browsing-context">browsing context</a>.</p>
 
-  </div><h5 id="link-type-pingback"><span class="secno">6.12.3.12 </span>Link type "<dfn title="rel-pingback"><code>pingback</code></dfn>"</h5><p>The <code title="rel-pingback"><a href="#link-type-pingback">pingback</a></code> keyword may be
+  </div><!-- v2: Would be nice to apply this to other elements too,
+  e.g. letting <img> or CSS or <video> hide the referrer --><h5 id="link-type-pingback"><span class="secno">6.12.3.12 </span>Link type "<dfn title="rel-pingback"><code>pingback</code></dfn>"</h5><p>The <code title="rel-pingback"><a href="#link-type-pingback">pingback</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>.<p>For the semantics of the <code title="rel-pingback"><a href="#link-type-pingback">pingback</a></code> keyword, see the Pingback 1.0
   specification. <a href="#references">[PINGBACK]</a><h5 id="link-type-prefetch"><span class="secno">6.12.3.13 </span>Link type "<dfn title="rel-prefetch"><code>prefetch</code></dfn>"</h5><p>The <code title="rel-prefetch"><a href="#link-type-prefetch">prefetch</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>.<p>The <code title="rel-prefetch"><a href="#link-type-prefetch">prefetch</a></code> keyword indicates
Received on Monday, 15 June 2009 01:10:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 15 June 2009 01:10:31 GMT