<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi folks,<br>
<br>
Bug 80713 is about having seamless iframes. Seamless iframes are
iframes which don't scroll, i.e. they have exactly the height of
their contents. This allows one to "seamlessly" inject foreing
content into a main document. We've been wanting this for <b>years</b>:<br>
- in
<a class="moz-txt-link-freetext" href="http://weblogs.mozillazine.org/asa/archives/2011/07/primary_thunderbird.html">http://weblogs.mozillazine.org/asa/archives/2011/07/primary_thunderbird.html</a>,
asuth remarks that one of asa's suggestions cannot be implemented
because 80713 blocks us,<br>
- <a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/show_bug.cgi?id=9942">https://bugzilla.mozilla.org/show_bug.cgi?id=9942</a> (vintage bug,
beware) is also blocked by 80713 — actually I think this is what
Andrew had in mind,<br>
- 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>
- I'm constantly hitting the bug in my code (Thunderbird
Conversations), because each message in the conversation is in its
own iframe, and that's the only way I can do it. I won't go into the
long list of gory hacks I've had to write, but I'm still hitting
issues that would all be solved by 80713 : the amount of workarounds
I'm writing to get around this is becoming ridiculous.<br>
- bwinton also mentions on the bug he wished twice he had that
feature.<br>
<br>
I can't possibly stress enough how this is blocking us in many
different areas, and for how long we've wished we had such a
feature.<br>
<br>
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>
<br>
Thus, my question is : is there anything we can do about it? Can we
possibly request that the bug be fixed, in some kind of an official
manner? Can we take some money off our budget to bribe roc into
fixing it? ;-) I don't think we make that kind of requests often,
and that's partly because we know we have close to zero weight in
the Gecko politics, but if there's anything we can do about it, I do
think it might be worth a try.<br>
<br>
Best,<br>
<br>
jonathan<br>
</body>
</html>