<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 07/04/2011 02:09 AM, Jonathan Protzenko wrote:
<blockquote cite="mid:4E115901.8020301@gmail.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
- if we were to rewrite libmime, we'd probably want HTML parts to
be in their own iframes, rather than having to process the html to
make it fit in the bigger html chunk of the whole message,<br>
</blockquote>
Also wonderful here would be sandboxed iframes, which (barring Gecko
bugs) would disable script rather than relying on our current
approach of sanitizing HTML.<br>
<blockquote cite="mid:4E115901.8020301@gmail.com" type="cite">I
remember reading an old thread on m.d.planning where Gecko devs
explicitly stated that Gecko was "the rendering engine for
Firefox", not other projects (can't find the exact quotation,
though), and they were not interested in fixing bugs / blocking
releases on bugs that didn't have a direct impact to /
relationship with Firefox.<br>
</blockquote>
<br>
Well, <iframe seamless> is an HTML 5 feature, and it's one
which we know to be not useless. So it's a feature which helps
Firefox, just not to the same degree that it helps Thunderbird.<br>
</body>
</html>