<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Dec 1, 2010, at 5:37 PM, Robert O'Callahan wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Thu, Dec 2, 2010 at 2:25 PM, Tab Atkins Jr. <span dir="ltr"><<a href="mailto:jackalmage@gmail.com">jackalmage@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, Dec 1, 2010 at 5:20 PM, Robert O'Callahan <<a href="mailto:robert@ocallahan.org">robert@ocallahan.org</a>> wrote:<br>
> In the absence of compelling use cases, I'd just leave it at <img>, <canvas><br>
> and <video> and whitelist in more elements later if necessary.<br>
<br>
</div><input type=image>? <object>/<embed> seem to have roughly equivalent<br>
use-cases to <video> (though perhaps we just want to encourage<br>
<video>).<br></blockquote><div><br><object> can contain fallback content which might get tricky.<br></div></div></blockquote><div><br></div>So can <video>.</div><div><br></div><div>It's a shame to disallow HTML elements with known width and height, e.g. if you want to render a small disconnected <div> subtree into a <canvas> or map it onto a WebGL texture. You'd have to decide how to resolve style (maybe assume it's a child of the body?).</div><div><br></div><div>Simon</div><div><br></div><div><br></div></body></html>