Why we need Gecko updates

Axel Grude axel.grude at gmail.com
Thu Dec 10 00:35:04 UTC 2015

Get Thunderbird!

> *Subject:* Re: Why we need Gecko updates
> *To:* Tb-planning
> *From: *Tanstaafl
> *Sent: *Wednesday, 09/12/2015 15:12:12 15:12 GMT ST +0000 [Week 49]
> On 12/9/2015 3:04 AM, Mihovil Stanić <mihovil at miho.im> wrote:
> > If remote servers are disabled by default and java script disabled in
> > email, how big threat are those vurnabilities?
> > That doesn't sound like a big threat to me, but I might be mistaken.
> >
> > Additionaly, I really don't see point in surfing webpages with TB.
> I agree, and I neglected to follow-up, but this - 'surfing web pages
> with TB' - is what I meant when I said the 'browser should be ripped out
> at its roots'...
> I understand that we need an HTML rendering engine for rendering HTML
> emails, but that should be a very stripped down engine, no need for a
> full blown browser engine. Personally, I don't see a problem with
> completely disabling JS in the rendering of the email itself (separate
> from magic done by Addons using JS)...

JS is for the chrome and Addons :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/tb-planning/attachments/20151210/cc194fb8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: thunderbird_blog2.png
Type: image/png
Size: 846 bytes
Desc: not available
URL: <http://mail.mozilla.org/pipermail/tb-planning/attachments/20151210/cc194fb8/attachment.png>

More information about the tb-planning mailing list