Last night (Friday), I recorded Part Two of a (I think) three part T.V.
series,
http://www.ebroadcast.com.au/tv/detail.php?id=17835978&fta=1&fox=0, and,
before I watched this, I was going to sit back this (Saturday) afternoon
and watch Part One (which I missed last Friday) of the series on my L
Frank-Rainer Grahl writes:
> They are all still open / unfixed.
>
Actually, I think this is a problem with an addon. (But I don't know
which one yet). :/
--
~
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozill
They are all still open / unfixed.
FRG
Richmond wrote:
Frank-Rainer Grahl writes:
If you know the/a specific bug number which changed this it could maybe
backported. Otherwise not.
I think it might be this:
https://bugzilla.mozilla.org/show_bug.cgi?id=1376536
which links to this:
https:
Settings: default values
mail.strictly_mime;false
mail.strictly_mime.parm_folding;1
mail.strictly_mime_headers;true
Received header:
---
MIME-Version: 1.0
Content-Type: application/pkcs7-mime; name="smime.p7m";
smime-type=enveloped-data
Content-Transfer-Encoding: base64
Content-Di
Frank-Rainer Grahl writes:
> If you know the/a specific bug number which changed this it could maybe
> backported. Otherwise not.
I think it might be this:
https://bugzilla.mozilla.org/show_bug.cgi?id=1376536
which links to this:
https://bugzilla.mozilla.org/show_bug.cgi?id=1398697
and
http
If you know the/a specific bug number which changed this it could maybe
backported. Otherwise not.
FRG
Richmond wrote:
Seamonkey uses much cpu on web.whatsapp.com (when logged in and viewing
chats). This also applies to firefox esr 52. But I have checked firefox
56 beta and that works fine. (
Seamonkey uses much cpu on web.whatsapp.com (when logged in and viewing
chats). This also applies to firefox esr 52. But I have checked firefox
56 beta and that works fine. (As does chromium). Is there a way to get
that fix back into 2.49.1 when it is released?
SM 2.49.1 compiled by me on Opensuse
7 matches
Mail list logo
