<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 14, 2009, at 3:43 AM, Robert O'Callahan wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Tue, Jul 14, 2009 at 10:42 PM, Robert O'Callahan <span dir="ltr"><<a href="mailto:robert@ocallahan.org">robert@ocallahan.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div class="im">On Tue, Jul 14, 2009 at 10:34 PM, Jonas Sicking <span dir="ltr"><<a href="mailto:jonas@sicking.cc">jonas@sicking.cc</a>></span> wrote:<br></div><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> We can do what's described above for videos and audios too (i.e. walk<br> parent chain etc).<br> </blockquote></div><div><br>We can hack something in, but what about dynamic DOM changes? IFRAME loads? etc <br></div></div><div><div></div></div></blockquote><div> </div></div>More importantly for this list, what should the spec say?<br clear="all"></blockquote></div><br><div>Clearly the desirable end result is that a <video> or <audio> element with fallback to an <object> or <embed> should not load or play the fallback content. I'm not sure how to spec this in a rigorous and consistent way.</div><div><br></div><div> - Maciej</div></body></html>