Annotate some possible hacks we'll have to add for <embed> and <object>. (whatwg r3288)

Annotate some possible hacks we'll have to add for <embed> and <object>.
(whatwg r3288)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2434&r2=1.2435&f=h
http://html5.org/tools/web-apps-tracker?from=3287&to=3288

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2434
retrieving revision 1.2435
diff -u -d -r1.2434 -r1.2435
--- Overview.html 16 Jun 2009 23:01:39 -0000 1.2434
+++ Overview.html 16 Jun 2009 23:04:13 -0000 1.2435
@@ -15787,7 +15787,7 @@
   <code><a href="#the-iframe-element">iframe</a></code> element's <a href="#nested-browsing-context">nested browsing
   context</a>.</p>
 
-  </div><h4 id="the-embed-element"><span class="secno">4.8.4 </span>The <dfn><code>embed</code></dfn> element</h4><!--
+  </div><h4 id="the-embed-element"><span class="secno">4.8.4 </span>The <dfn><code>embed</code></dfn> element</h4><!-- (v2?)
  we have all kinds of quirks we should define if they come up during
  testing, as e.g. shown in:
  http://mxr.mozilla.org/mozilla-central/source/layout/generic/nsObjectFrame.cpp
@@ -16076,6 +16076,21 @@
 
    </li>
 
+   <!-- (v2?)
+   we may have to define magic fallback to <param> if it turns out to
+   be needed in testing:
+   <hyatt> apparently your url can come from <param>
+   <hyatt> not just the data attribute
+   <hyatt> our code looks for params with "src", "movie", "code" and "url"
+   <hyatt> and also tries to find the type on a param
+   <Hixie> oh that's you trying to have hacky activex support
+   <Hixie> opera does that too
+   <hyatt> yeah we support activex versions of plugins that are common
+   <hyatt> like flash and quicktime and realaudio
+   <Hixie> that would be a step 1b. if no data attribute, then look for a <param> to get you a URL instead.
+   <Hixie> and if you find one, carry on as if that was your data="".
+   -->
+
    <li><p>If the <code title="attr-object-data"><a href="#attr-object-data">data</a></code> attribute
    is present, then:</p>
 
@@ -16315,19 +16330,6 @@
   different capabilities, with the user agent picking the first one it
   supports.</p>
 
-<!-- XXX
-<hyatt> apparently your url can come from <param>
-<hyatt> not just the data attribute
-<hyatt> our code looks for params with "src", "movie", "code" and "url"
-<hyatt> and also tries to find the type on a param
-<Hixie> oh that's you trying to have hacky activex support
-<Hixie> opera does that too
-<hyatt> yeah we support activex versions of plugins that are common
-<hyatt> like flash and quicktime and realaudio
-<Hixie> that would be a step 1b. if no data attribute, then look for a <param> to get you a URL instead.
-<Hixie> and if you find one, carry on as if that was your data="".
--->
-
   <p>Whenever the <code title="attr-object-name"><a href="#attr-object-name">name</a></code> attribute
   is set, if the <code><a href="#the-object-element">object</a></code> element has a nested
   <a href="#browsing-context">browsing context</a>, its <a href="#browsing-context-name" title="browsing context

Received on Tuesday, 16 June 2009 23:05:06 UTC