<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Leif,<div><br><div><div>On Aug 21, 2008, at 12:11 PM, Robert J Burns wrote:</div><blockquote type="cite"><div>On Aug 21, 2008, at 6:15 AM, Leif Halvard Silli wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite">IN IE 6 the statement seems correct. And after having installed<br></blockquote><blockquote type="cite">IE8beta, it seems you are right in that it is not correct for IE8<br></blockquote><blockquote type="cite">... (Have not tried IE7, and do not trust the IE7 emulation of<br></blockquote><blockquote type="cite">IE8.) However, a better test case than yours is this (since in<br></blockquote><blockquote type="cite">your test, in IE8beta1, the GIF would actually be displayed):<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><object data="data:application/x-unknown,ERROR" ><br></blockquote><blockquote type="cite"><object type="image/gif" data="object-ie8.gif" ><br></blockquote><blockquote type="cite">some fallback</object></object<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Either they were wrong, or we misunderstands the issue ... I<br></blockquote><blockquote type="cite">wonder if they mean that if an OBJECT with an working<br></blockquote><blockquote type="cite">data="attribute" URI is found, then then the other nested OBJECTS<br></blockquote><blockquote type="cite">and the rest of the fallback content is ignored.<br></blockquote><br>Well, if an object is reached that IE can handle natively or through a <br>plugin handler, then that is what the HTML4.01 recommendation expects. <br>The issue is if you view the DOM, do you see the descendant nodes <br>there. If so then a sophisticated add-on or screen reader (something <br>like Fire Vox for example, though it is for Firefox) can get to the <br>fallback for accessibility reasons. In other words the DOM should look <br>something like:<br><br>HTML<br><span class="Apple-tab-span" style="white-space:pre"> </span>• HEAD<br><span class="Apple-tab-span" style="white-space:pre"> </span>• BODY<br><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>• OBJECT data="data:application/x-unknown,ERROR"<br><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>• #text:<br><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>• OBJECT type="image/gif" data="object-ie8.gif"<br><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>• #text: some fallback<br><br>If that's all there in IE, and IE selects the first supported or <br>enabled mime type in hierarchical order, then that's all we would <br>expect (since IE has no aural/braille features of its own).<br></div></blockquote><br></div><div>It occurs to me that the IE blogger may have simply been saying that they don't support alterante fallback in a different way. For example if the first file is application/xhtml+xml, and the resource is available, IE may instead resort to downloading it rather than falling back to the next OBJECT. Or maybe they do not support more than two fallbacks. Or maybe they're just saying that they don't offer user options to disable certain types of content (like for accessibility reasons). It is difficult to figure out what they could mean there[1].</div><div><br></div><div>Take care,</div><div>Rob</div><div><br></div><div>[1]: See "Known issues we are not planning to change in IE8" in the official Internet Explorer blog on the OBJECT element. <<a href="http://blogs.msdn.com/ie/archive/2008/04/10/html-and-dom-standards-compliance-in-ie8-beta-1.aspx">http://blogs.msdn.com/ie/archive/2008/04/10/html-and-dom-standards-compliance-in-ie8-beta-1.aspx</a>></div><div class=""><br></div></div></body></html>