[html5] r1654 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2008-05-20 22:08:13 -0700 (Tue, 20 May 2008)
New Revision: 1654

Modified:
   index
   source
Log:
[e] (0) More examples for the new features.

Modified: index
===================================================================
--- index	2008-05-21 04:40:44 UTC (rev 1653)
+++ index	2008-05-21 05:08:13 UTC (rev 1654)
@@ -14396,6 +14396,18 @@
     attribute.</p>
   </div>
 
+  <div class=example>
+   <p>In this example, a gadget from another site is embedded. The gadget has
+    scripting and forms enabled, and the origin sandbox restrictions are
+    lifted, allowing the gadget to communicate with its originating server.
+    The sandbox is still useful, however, as it disables plugins and popups,
+    thus reducing the risk of the user being exposed to malware and other
+    annoyances.</p>
+
+   <pre><iframe sandbox="allow-same-origin allow-forms allow-scripts"
+        src="http://maps.example.com/embedded.html"></iframe></pre>
+  </div>
+
   <hr>
 
   <p>The <dfn id=seamless
@@ -14502,6 +14514,23 @@
    href="#nested0">nested browsing context</a> is <a href="#navigate"
    title=navigate>navigated</a> to another origin.
 
+  <div class=example>
+   <p>In this example, the site's navigation is embedded using a client-side
+    include using an <code><a href="#iframe">iframe</a></code>. Any links in
+    the <code><a href="#iframe">iframe</a></code> will, in new user agents,
+    be automatically opened in the <code><a
+    href="#iframe">iframe</a></code>'s parent browsing context; for legacy
+    user agents, the site could also include a <code><a
+    href="#base">base</a></code> element with a <code
+    title=attr-base-target><a href="#target">target</a></code> attribute with
+    the value <code title="">_parent</code>. Similarly, in new user agents
+    the styles of the parent page will be automatically applied to the
+    contents of the frame, but to support legacy user agents authors might
+    wish to include the styles explicitly.</p>
+
+   <pre><nav><iframe seamless src="nav.include.html"></iframe></nav></pre>
+  </div>
+
   <hr>
 
   <p>An <code><a href="#iframe">iframe</a></code> element never has <a

Modified: source
===================================================================
--- source	2008-05-21 04:40:44 UTC (rev 1653)
+++ source	2008-05-21 05:08:13 UTC (rev 1654)
@@ -12442,8 +12442,22 @@
 
   </div>
 
+  <div class="example">
 
+   <p>In this example, a gadget from another site is embedded. The
+   gadget has scripting and forms enabled, and the origin sandbox
+   restrictions are lifted, allowing the gadget to communicate with
+   its originating server. The sandbox is still useful, however, as it
+   disables plugins and popups, thus reducing the risk of the user
+   being exposed to malware and other annoyances.</p>
 
+   <pre><iframe sandbox="allow-same-origin allow-forms allow-scripts"
+        src="http://maps.example.com/embedded.html"></iframe></pre>
+
+  </div>
+
+
+
   <hr>
 
 
@@ -12548,8 +12562,30 @@
   gets unset if the <span>nested browsing context</span> is <span
   title="navigate">navigated</span> to another origin.</p>
 
+  <div class="example">
+
+   <p>In this example, the site's navigation is embedded using a
+   client-side include using an <code>iframe</code>. Any links in the
+   <code>iframe</code> will, in new user agents, be automatically
+   opened in the <code>iframe</code>'s parent browsing context; for
+   legacy user agents, the site could also include a <code>base</code>
+   element with a <code title="attr-base-target">target</code>
+   attribute with the value <code title="">_parent</code>. Similarly,
+   in new user agents the styles of the parent page will be
+   automatically applied to the contents of the frame, but to support
+   legacy user agents authors might wish to include the styles
+   explicitly.</p>
+
+   <pre><nav><iframe seamless src="nav.include.html"></iframe></nav></pre>
+
+  </div>
+
+
+
   <hr>
 
+
+
   <p>An <code>iframe</code> element never has <span>fallback
   content</span>, as it will always create a nested <span>browsing
   context</span>, regardless of whether the specified initial contents