Mail date format changed in 2.53.1

2020-03-07 Thread Manuel Casal Lodeiro
Sorry if this has been pointed out in some previous message. I looked at 
the subjects and I found no reference. So here it goes:


The locale format in message headers (in Thread pane in Mail window) has 
changed from previous versions after updating to 2.53.1.


I'm using Linux version, with Ubuntu 18.04.4 LTS.

It's very strange, because I don't remember Seamonkey or Mozilla suite 
or Netscape *ever* changing this.


I've taken a look at about:config but I couldn't find where to change 
this back to my locale format DD/MM/YY. Now it's been changed to MM/DD/YY.


Any help would be appreciated. Thanks!
--
< Manuel Casal Lodeiro, (a) «Casdeiro» >

«We approach winter the most depressing period in the history
of this industrial empire, with threats of oil shortages and
energy crises. But we, as Black people, have been a source of
endless energy, endless beauty and endless determination. I
have many things to tell you about tomorrow’s love and light.
We will see you in Spring.»

  — Gil Scott-Heron (Winter in America, 1974)

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: SM already has a clone tab -- Re: For those who use PrefBar v7.1.1, does its clone button not work anymore for you too?

2020-03-07 Thread Ant

On 3/7/2020 6:43 PM, alexyu wrote:

Frank-Rainer Grahl wrote, on 07 Mar 20 20:16:


alexyu wrote:

I commented on using "Duplicate Tab", which I have been using since 
before FF (and, I think, SM too) introduced the "middle-click on 
'reload' button" for this.  Not having a middle-button on my mouse, 
I've read that clicking on the wheel might work, but on my muse it 
doesn't, neither in SM nor in FF -- so I keep using "Duplicate Tab", 
which also has other functionalities, as I mentioned.


And, again: I still haven't tried it in SM 2.53, because I have to 
prepare first (as should anyone considering the move).


Will not work. The clone methods are not (yet) implemented in 
SeaMonkeys tab browser code.


Thanks, FRG; you've just saved me a lot of work:  Since "Duplicate Tab" 
is very useful to me, knowing in advance that it won't work in SM 2.53 
means that I won't even try the migration -- instead, I'll stay on 
2.49.5 for the foreseeable future.


You could just control or middle mouse button click on web browser's 
reload button in v2.53.1. I don't know if v2.49.5 and earlier versions 
can do that too since I don't have them anymore.

--
"An ant on the move does more than a dozing ox." --Mexican Proverb
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ http://aqfl.net & http://antfarm.ma.cx /
  / /\ /\ \ http://antfarm.home.dhs.org
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: SM already has a clone tab -- Re: For those who use PrefBar v7.1.1, does its clone button not work anymore for you too?

2020-03-07 Thread alexyu

Frank-Rainer Grahl wrote, on 07 Mar 20 20:16:


alexyu wrote:

I commented on using "Duplicate Tab", which I have been using since 
before FF (and, I think, SM too) introduced the "middle-click on 
'reload' button" for this.  Not having a middle-button on my mouse, 
I've read that clicking on the wheel might work, but on my muse it 
doesn't, neither in SM nor in FF -- so I keep using "Duplicate Tab", 
which also has other functionalities, as I mentioned.


And, again: I still haven't tried it in SM 2.53, because I have to 
prepare first (as should anyone considering the move).


Will not work. The clone methods are not (yet) implemented in SeaMonkeys 
tab browser code.


Thanks, FRG; you've just saved me a lot of work:  Since "Duplicate Tab" 
is very useful to me, knowing in advance that it won't work in SM 2.53 
means that I won't even try the migration -- instead, I'll stay on 
2.49.5 for the foreseeable future.


--
Best,

s) alexyu   



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: SM already has a clone tab -- Re: For those who use PrefBar v7.1.1, does its clone button not work anymore for you too?

2020-03-07 Thread Frank-Rainer Grahl

alexyu wrote:

Ant wrote, on 07 Mar 20 17:34:


On 3/6/2020 9:45 PM, Ant wrote:

When I clone a loaded web page tab, I get a blank tab titled "Untitled". It 
used to work in SeaMonkey v2.49.5 and earlier versions in both my decade 
old 64-bit W7 HPE SP1 and 12 years old Linux/Debian Jessie v8 PC. Maybe its 
code needs to be updated? :(


Thank you for reading and hopefully answering. :)


Yesterday, I e-mailed Manuel Reimer about this issue. He said "... in 
Firefox you can clone a tab by middle-clicking on the 'reload'

button. Also works with 'Ctrl+Click'. So there is no need for an addon
doing this.

I don't know if this works in SeaMonkey, too. Currently I don't use it."

Both methods worked. I never knew these two tricks! Did you? I wished SM had 
clone tab option visually like a menu option, button, or something! I can't 
remember all these hot keys and gestures!


Since you changed the 'about' and quoted a message outside this thread, I 
don't know if you're answering my reply to you, just above, or posted this 
without seeing it.


I commented on using "Duplicate Tab", which I have been using since before FF 
(and, I think, SM too) introduced the "middle-click on 'reload' button" for 
this.  Not having a middle-button on my mouse, I've read that clicking on the 
wheel might work, but on my muse it doesn't, neither in SM nor in FF -- so I 
keep using "Duplicate Tab", which also has other functionalities, as I mentioned.


And, again: I still haven't tried it in SM 2.53, because I have to prepare 
first (as should anyone considering the move).




Will not work. The clone methods are not (yet) implemented in SeaMonkeys tab 
browser code.


FRG
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Lightning extension and cookies

2020-03-07 Thread Frank-Rainer Grahl

user wrote:


Hello

It seems to exist a relation between the Ligntning extension and cookies in 
Seamonkey.


On most websites, there is no problem. But with some, there is a cookies 
problem when Lightning extension is enabled.
In such a case, it is not possible to log in, or to add products in the 
basket, and the website ask for enabling cookies in the browser.


All is ok when the Lightning extension is disabled.

The problem is the same with 2.53.1 and 2.49.5
Not tested with older Seamonkey versions.

Also checked with the same result on another computer, and with a brand new 
profile.


Why does the Lightning extension change the behaviour of the cookies in the 
browser ?


Disable "Advertize Lightning" in preferences: Advanced->HTTP Networking.

FRG
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Building Seamonkey 2.53.1 error on nsstring v0.1.0, both on Devuan and on Arch Linux

2020-03-07 Thread Frank-Rainer Grahl

hjhe...@gmail.com wrote:

On Saturday, 7 March 2020 23:27:45 UTC+1, hjh...@gmail.com  wrote:

Hi All,

I hope someone here is familiar with this issue and can point me in the right 
direction. I have been trying to build Seamonkey 2.53.1 for a while now, but to 
no avail. Whichever mozconfig settings I take, I always get kicked off the 
build with an error on nsstring v0.10.
The error is:

__

Compiling nsstring v0.1.0 
(/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring)
error: use of deprecated item 'try': use the `?` operator instead
--> 
/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:138:5
 |
138 | / bitflags! {
139 | | // While this has the same layout as u16, it cannot be passed
140 | | // over FFI safely as a u16.
141 | | #[repr(C)]
...   |
149 | | }
150 | | }
 | |_^
 |
note: lint level defined here
--> 
/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:116:9
 |
116 | #![deny(warnings)]
 | 
 = note: `#[deny(deprecated)]` implied by `#[deny(warnings)]`
 = note: this error originates in a macro outside of the current crate (in 
Nightly builds, run with -Z external-macro-backtrace for more info)

error: use of deprecated item 'try': use the `?` operator instead
--> 
/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:138:5
 |
138 | / bitflags! {
139 | | // While this has the same layout as u16, it cannot be passed
140 | | // over FFI safely as a u16.
141 | | #[repr(C)]
...   |
149 | | }
150 | | }
 | |_^
 |
 = note: this error originates in a macro outside of the current crate (in 
Nightly builds, run with -Z external-macro-backtrace for more info)

error: use of deprecated item 'try': use the `?` operator instead
--> 
/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:154:5
 |
154 | / bitflags! {
155 | | // While this has the same layout as u16, it cannot be passed
156 | | // over FFI safely as a u16.
157 | | #[repr(C)]
...   |
161 | | }
162 | | }
 | |_^
 |
 = note: this error originates in a macro outside of the current crate (in 
Nightly builds, run with -Z external-macro-backtrace for more info)

error: use of deprecated item 'try': use the `?` operator instead
--> 
/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:154:5
 |
154 | / bitflags! {
155 | | // While this has the same layout as u16, it cannot be passed
156 | | // over FFI safely as a u16.
157 | | #[repr(C)]
...   |
161 | | }
162 | | }
 | |_^
 |
 = note: this error originates in a macro outside of the current crate (in 
Nightly builds, run with -Z external-macro-backtrace for more info)

error: aborting due to 4 previous errors

error: could not compile `nsstring`.

___

Could someone please tell me what I am doing wrong? I have cargo and rustc 
installed, and am compiling with gcc.

Thank you for any input!

regards,

Hendrik-Jan Heins


Not sure if it is impportant: gcc on Arch is 9.2.0, on Debian 8.3.0.
But both produce the same error (as mentioned above)



Use rust 1.36. rust 1.37 might also work.

FRG
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Amazon's Smile?

2020-03-07 Thread WaltS48 via support-seamonkey

Ant wrote:
I noticed SeaMonkey isn't in Amazon's Smile 
(https://smile.amazon.com/gp/chpf/homepage?q=seamonkey=%2F=UTF-8), 
but Mozilla is. Does donating to Mozilla go to SeaMonkey at all? If not, 
then SeaMonkey needs to be in that Smile! :)


Thank you for reading and hopefully answering. :)



You are aware that SeaMonkey is used by probably less than 100,000 users 
at last ADI stats available from Mozilla.


It isn't a major browser and anything you donate to Mozilla doesn't go 
to SeaMonkey or Thunderbird.


You donate to SeaMonkey by smushing the "Donate" button on 
 which takes the smusher to 


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Building Seamonkey 2.53.1 error on nsstring v0.1.0, both on Devuan and on Arch Linux

2020-03-07 Thread hjheins
On Saturday, 7 March 2020 23:27:45 UTC+1, hjh...@gmail.com  wrote:
> Hi All,
> 
> I hope someone here is familiar with this issue and can point me in the right 
> direction. I have been trying to build Seamonkey 2.53.1 for a while now, but 
> to no avail. Whichever mozconfig settings I take, I always get kicked off the 
> build with an error on nsstring v0.10.
> The error is:
> 
> __
> 
>Compiling nsstring v0.1.0 
> (/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring)
> error: use of deprecated item 'try': use the `?` operator instead
>--> 
> /home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:138:5
> |
> 138 | / bitflags! {
> 139 | | // While this has the same layout as u16, it cannot be passed
> 140 | | // over FFI safely as a u16.
> 141 | | #[repr(C)]
> ...   |
> 149 | | }
> 150 | | }
> | |_^
> |
> note: lint level defined here
>--> 
> /home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:116:9
> |
> 116 | #![deny(warnings)]
> | 
> = note: `#[deny(deprecated)]` implied by `#[deny(warnings)]`
> = note: this error originates in a macro outside of the current crate (in 
> Nightly builds, run with -Z external-macro-backtrace for more info)
> 
> error: use of deprecated item 'try': use the `?` operator instead
>--> 
> /home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:138:5
> |
> 138 | / bitflags! {
> 139 | | // While this has the same layout as u16, it cannot be passed
> 140 | | // over FFI safely as a u16.
> 141 | | #[repr(C)]
> ...   |
> 149 | | }
> 150 | | }
> | |_^
> |
> = note: this error originates in a macro outside of the current crate (in 
> Nightly builds, run with -Z external-macro-backtrace for more info)
> 
> error: use of deprecated item 'try': use the `?` operator instead
>--> 
> /home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:154:5
> |
> 154 | / bitflags! {
> 155 | | // While this has the same layout as u16, it cannot be passed
> 156 | | // over FFI safely as a u16.
> 157 | | #[repr(C)]
> ...   |
> 161 | | }
> 162 | | }
> | |_^
> |
> = note: this error originates in a macro outside of the current crate (in 
> Nightly builds, run with -Z external-macro-backtrace for more info)
> 
> error: use of deprecated item 'try': use the `?` operator instead
>--> 
> /home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:154:5
> |
> 154 | / bitflags! {
> 155 | | // While this has the same layout as u16, it cannot be passed
> 156 | | // over FFI safely as a u16.
> 157 | | #[repr(C)]
> ...   |
> 161 | | }
> 162 | | }
> | |_^
> |
> = note: this error originates in a macro outside of the current crate (in 
> Nightly builds, run with -Z external-macro-backtrace for more info)
> 
> error: aborting due to 4 previous errors
> 
> error: could not compile `nsstring`.
> 
> ___
> 
> Could someone please tell me what I am doing wrong? I have cargo and rustc 
> installed, and am compiling with gcc.
> 
> Thank you for any input!
> 
> regards,
> 
> Hendrik-Jan Heins

Not sure if it is impportant: gcc on Arch is 9.2.0, on Debian 8.3.0.
But both produce the same error (as mentioned above)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Building Seamonkey 2.53.1 error on nsstring v0.1.0, both on Devuan and on Arch Linux

2020-03-07 Thread hjheins
Hi All,

I hope someone here is familiar with this issue and can point me in the right 
direction. I have been trying to build Seamonkey 2.53.1 for a while now, but to 
no avail. Whichever mozconfig settings I take, I always get kicked off the 
build with an error on nsstring v0.10.
The error is:

__

   Compiling nsstring v0.1.0 
(/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring)
error: use of deprecated item 'try': use the `?` operator instead
   --> 
/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:138:5
|
138 | / bitflags! {
139 | | // While this has the same layout as u16, it cannot be passed
140 | | // over FFI safely as a u16.
141 | | #[repr(C)]
...   |
149 | | }
150 | | }
| |_^
|
note: lint level defined here
   --> 
/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:116:9
|
116 | #![deny(warnings)]
| 
= note: `#[deny(deprecated)]` implied by `#[deny(warnings)]`
= note: this error originates in a macro outside of the current crate (in 
Nightly builds, run with -Z external-macro-backtrace for more info)

error: use of deprecated item 'try': use the `?` operator instead
   --> 
/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:138:5
|
138 | / bitflags! {
139 | | // While this has the same layout as u16, it cannot be passed
140 | | // over FFI safely as a u16.
141 | | #[repr(C)]
...   |
149 | | }
150 | | }
| |_^
|
= note: this error originates in a macro outside of the current crate (in 
Nightly builds, run with -Z external-macro-backtrace for more info)

error: use of deprecated item 'try': use the `?` operator instead
   --> 
/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:154:5
|
154 | / bitflags! {
155 | | // While this has the same layout as u16, it cannot be passed
156 | | // over FFI safely as a u16.
157 | | #[repr(C)]
...   |
161 | | }
162 | | }
| |_^
|
= note: this error originates in a macro outside of the current crate (in 
Nightly builds, run with -Z external-macro-backtrace for more info)

error: use of deprecated item 'try': use the `?` operator instead
   --> 
/home/hjheins/build/Seamonkey/src/seamonkey-2.53.1/mozilla/xpcom/rust/nsstring/src/lib.rs:154:5
|
154 | / bitflags! {
155 | | // While this has the same layout as u16, it cannot be passed
156 | | // over FFI safely as a u16.
157 | | #[repr(C)]
...   |
161 | | }
162 | | }
| |_^
|
= note: this error originates in a macro outside of the current crate (in 
Nightly builds, run with -Z external-macro-backtrace for more info)

error: aborting due to 4 previous errors

error: could not compile `nsstring`.

___

Could someone please tell me what I am doing wrong? I have cargo and rustc 
installed, and am compiling with gcc.

Thank you for any input!

regards,

Hendrik-Jan Heins
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Lightning extension and cookies

2020-03-07 Thread user



Hello

It seems to exist a relation between the Ligntning extension and cookies 
in Seamonkey.


On most websites, there is no problem. But with some, there is a cookies 
problem when Lightning extension is enabled.
In such a case, it is not possible to log in, or to add products in the 
basket, and the website ask for enabling cookies in the browser.


All is ok when the Lightning extension is disabled.

The problem is the same with 2.53.1 and 2.49.5
Not tested with older Seamonkey versions.

Also checked with the same result on another computer, and with a brand 
new profile.


Why does the Lightning extension change the behaviour of the cookies in 
the browser ?

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: SM already has a clone tab -- Re: For those who use PrefBar v7.1.1, does its clone button not work anymore for you too?

2020-03-07 Thread alexyu

Ant wrote, on 07 Mar 20 17:34:


On 3/6/2020 9:45 PM, Ant wrote:

When I clone a loaded web page tab, I get a blank tab titled 
"Untitled". It used to work in SeaMonkey v2.49.5 and earlier versions 
in both my decade old 64-bit W7 HPE SP1 and 12 years old Linux/Debian 
Jessie v8 PC. Maybe its code needs to be updated? :(


Thank you for reading and hopefully answering. :)


Yesterday, I e-mailed Manuel Reimer about this issue. He said "... in 
Firefox you can clone a tab by middle-clicking on the 'reload'

button. Also works with 'Ctrl+Click'. So there is no need for an addon
doing this.

I don't know if this works in SeaMonkey, too. Currently I don't use it."

Both methods worked. I never knew these two tricks! Did you? I wished SM 
had clone tab option visually like a menu option, button, or something! 
I can't remember all these hot keys and gestures!


Since you changed the 'about' and quoted a message outside this thread, 
I don't know if you're answering my reply to you, just above, or posted 
this without seeing it.


I commented on using "Duplicate Tab", which I have been using since 
before FF (and, I think, SM too) introduced the "middle-click on 
'reload' button" for this.  Not having a middle-button on my mouse, I've 
read that clicking on the wheel might work, but on my muse it doesn't, 
neither in SM nor in FF -- so I keep using "Duplicate Tab", which also 
has other functionalities, as I mentioned.


And, again: I still haven't tried it in SM 2.53, because I have to 
prepare first (as should anyone considering the move).


--
Best,

s) alexyu   



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Amazon's Smile?

2020-03-07 Thread Ant
I noticed SeaMonkey isn't in Amazon's Smile 
(https://smile.amazon.com/gp/chpf/homepage?q=seamonkey=%2F=UTF-8), 
but Mozilla is. Does donating to Mozilla go to SeaMonkey at all? If not, 
then SeaMonkey needs to be in that Smile! :)


Thank you for reading and hopefully answering. :)
--
"I killed an ant, now all my relatives are afraid of me." --unknown
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ http://aqfl.net & http://antfarm.ma.cx /
  / /\ /\ \ http://antfarm.home.dhs.org
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Blocking bad stuff (was Re: Is there a way to know which extensions may break when upgrading?)

2020-03-07 Thread Ant

On 3/7/2020 4:17 AM,  Mr. Ed  wrote:
...

No ad blocker, horsey? :/


Yeh, done by the usage of the Windows 'hosts' file:
http://someonewhocares.org/hosts/


Ah. Does using hosts mostly work? I have to use all! Hosts, web 
browsers' ad blockers, etc.

--
"If I find one beer can in that car, it's over!" --Red; "And no donuts 
either! Ants!" --Kitty from That '70s Show pilot
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ http://aqfl.net & http://antfarm.ma.cx /
  / /\ /\ \ http://antfarm.home.dhs.org
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Is there a way to know which extensions may break when upgrading?

2020-03-07 Thread Ant

On 3/7/2020 11:47 AM, EE wrote:

Steve Dunn wrote:
 There seems to be a fair bit of potential for extensions that 
work in 2.49.x to break in 2.53.1, based on what people have been 
posting here. I can't say I'm surprised, given that the developers 
have to try to maintain compatibility with an obsolete extension 
system while grafting in components from a browser that moved to a 
modern extension system a few years ago, but since extensions are 
important, it's kind of a problem if the stop working.


 Is there a way to know for sure which of your favourite 
extensions will work in 2.53.1, or is it a case of back up, hope for 
the best, and be prepared to uninstall 2.53.1, reinstall 2.49.5, and 
restore your backup?


-Steve


Back up the profile first before you upgrade.  You can then restore it 
before going back to the older version.


Or make a new SM installation and profile?
--
"If I find one beer can in that car, it's over!" --Red; "And no donuts 
either! Ants!" --Kitty from That '70s Show pilot
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ http://aqfl.net & http://antfarm.ma.cx /
  / /\ /\ \ http://antfarm.home.dhs.org
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Is there a way to know which extensions may break when upgrading?

2020-03-07 Thread Ant

On 3/7/2020 7:49 AM, Steve Dunn wrote:

On 2020-03-06 18:09, Ant wrote:
You could share what extensions you have and we can tell you. Here's 
mine:


 The most important ones for me are:

* JunQuilla 1.0.4
* Adblock Plus 2.9.1 (which the 2.53.1 release notes say is problematic, 
but someone else in this thread is also using)

* HTTPS Everywhere 5.2.20

 I stopped using SeaMonkey for most browsing a couple of years ago - 
Firefox is so much faster, has fewer sites that refuse to work with it, 
gets security updates much more promptly, and doesn't have to rely on 
obsolete extensions.  I mostly use SeaMonkey for email and newsgroups, 
and if some of my other extensions break, I can deal with it.


I still use SM mostly, but once in a while I have to use the 
(lat/new)est Firefox. :(

--
"If I find one beer can in that car, it's over!" --Red; "And no donuts 
either! Ants!" --Kitty from That '70s Show pilot
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ http://aqfl.net & http://antfarm.ma.cx /
  / /\ /\ \ http://antfarm.home.dhs.org
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


SM already has a clone tab -- Re: For those who use PrefBar v7.1.1, does its clone button not work anymore for you too?

2020-03-07 Thread Ant

On 3/6/2020 9:45 PM, Ant wrote:
When I clone a loaded web page tab, I get a blank tab titled "Untitled". 
It used to work in SeaMonkey v2.49.5 and earlier versions in both my 
decade old 64-bit W7 HPE SP1 and 12 years old Linux/Debian Jessie v8 PC. 
Maybe its code needs to be updated? :(


Thank you for reading and hopefully answering. :)


Yesterday, I e-mailed Manuel Reimer about this issue. He said "... in 
Firefox you can clone a tab by middle-clicking on the 'reload'

button. Also works with 'Ctrl+Click'. So there is no need for an addon
doing this.

I don't know if this works in SeaMonkey, too. Currently I don't use it."


Both methods worked. I never knew these two tricks! Did you? I wished SM 
had clone tab option visually like a menu option, button, or something! 
I can't remember all these hot keys and gestures!

--
"If I find one beer can in that car, it's over!" --Red; "And no donuts 
either! Ants!" --Kitty from That '70s Show pilot
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ http://aqfl.net & http://antfarm.ma.cx /
  / /\ /\ \ http://antfarm.home.dhs.org
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.53.1's about:crashes' report ID link doesn't work.

2020-03-07 Thread Ant

On 3/7/2020 3:20 AM, Frank-Rainer Grahl wrote:
...
Should work soon again. We and Thunderbird need to find a new 
crashserver home in August/September. It would have been nicce if 
someeone had told us before blocking anything above 2.49.5 but can't be 
helped.


https://bugzilla.mozilla.org/show_bug.cgi?id=1619101

When the bug is closed unsent crash reports can then be send if you 
doubleclick on them in about:crashes.


Thank you, FRG. :)
--
"If I find one beer can in that car, it's over!" --Red; "And no donuts 
either! Ants!" --Kitty from That '70s Show pilot
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ http://aqfl.net & http://antfarm.ma.cx /
  / /\ /\ \ http://antfarm.home.dhs.org
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Is there a way to know which extensions may break when upgrading?

2020-03-07 Thread EE

Ant wrote:

On 3/6/2020 2:37 PM, Steve Dunn wrote:
 There seems to be a fair bit of potential for extensions that 
work in 2.49.x to break in 2.53.1, based on what people have been 
posting here. I can't say I'm surprised, given that the developers 
have to try to maintain compatibility with an obsolete extension 
system while grafting in components from a browser that moved to a 
modern extension system a few years ago, but since extensions are 
important, it's kind of a problem if the stop working.


 Is there a way to know for sure which of your favourite 
extensions will work in 2.53.1, or is it a case of back up, hope for 
the best, and be prepared to uninstall 2.53.1, reinstall 2.49.5, and 
restore your backup?


You could share what extensions you have and we can tell you. Here's mine:

Last updated: Fri Mar 06 2020 15:08:50 GMT-0800 (Pacific Standard Time)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) 
Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.1


Extensions (enabled: 6)
* ColorfulTabs 31.1.9 (http://www.addongenie.com/colorfultabs)
* DOM Inspector 2.0.17.2 (http://www.mozilla.org/projects/inspector/)
* Expire history by days [converted] 1.2.0
* Open With 6.8.6 (https://github.com/darktrojan/openwith)
* PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)
* uBlock Origin 1.16.4.19 
(https://github.com/gorhill/uBlock-for-firefox-legacy)


I found that Restart App Button, Add-ons Button, and Cookie Monster no 
longer work after I updated to 2.53.
Chromedit Plus gives you a restart button, and CookieFast works.  I was 
unable to find another add-on button that works.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Is there a way to know which extensions may break when upgrading?

2020-03-07 Thread EE

Steve Dunn wrote:
 There seems to be a fair bit of potential for extensions that work 
in 2.49.x to break in 2.53.1, based on what people have been posting 
here. I can't say I'm surprised, given that the developers have to try 
to maintain compatibility with an obsolete extension system while 
grafting in components from a browser that moved to a modern extension 
system a few years ago, but since extensions are important, it's kind of 
a problem if the stop working.


 Is there a way to know for sure which of your favourite extensions 
will work in 2.53.1, or is it a case of back up, hope for the best, and 
be prepared to uninstall 2.53.1, reinstall 2.49.5, and restore your backup?


-Steve


Back up the profile first before you upgrade.  You can then restore it 
before going back to the older version.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: For those who use PrefBar v7.1.1, does its clone button not work anymore for you too?

2020-03-07 Thread alexyu

Ant wrote, on 07 Mar 20 02:45:

When I clone a loaded web page tab, I get a blank tab titled "Untitled". 
It used to work in SeaMonkey v2.49.5 and earlier versions in both my 
decade old 64-bit W7 HPE SP1 and 12 years old Linux/Debian Jessie v8 PC. 
Maybe its code needs to be updated? :(


Thank you for reading and hopefully answering. :)


"With Duplicate Tab you can copy a tab so that the copy has the same 
history of the original tab. A tab can be copied into a new tab or a new 
window. Other features available are "Merge Windows" which moves all 
tabs from all windows in to one single window, and "Detach Tab" which 
makes a window out of a tab. All actions can be invoked by toolbar 
buttons, shortcut keys and context menu items."


Duplicate Tab 1.0.2 (and other extensions from the same author) can be 
found at .


The only 'caveat' is that I still haven't tried it with SM 2.53. It's 
supposed to be compatible with FF 2.0-3.1a1pre and SM 1.1-2.0a1, but I 
can attest that it works fine in SM 2.49.5 and FF 52.7.4ESR.


--
Best,

s) alexyu   



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Sea monkey transfer to bigger tank

2020-03-07 Thread EE

t...@corporateknights.com wrote:

Hi I have my sea monkeys in a mason jar (500ml). They are about one month old 
and more than 1 CM, but just 5 of them survived.

I would like to transfer them to a 1.5 litre mason jar but do not want to hurt 
them.

Below is my plan--is this is the right way?
Fill my 1.5 litre mason with 1 litre of bottled water. Add a packet of water 
purifier. Wait 24 hours. Add the 500ml along with the 5 sea monkeys from the 
existing 500ml mason jar.

Then continue to feed them every few days with the small scoop of growth food.

Is that correct?

Thank you,

Toby


This group is about an internet suite, not about pets.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: No empty master password allowed in FIPS Software Security Device

2020-03-07 Thread Ricardo Palomares Martí­nez
El 5/3/20 a las 22:13, David E. Ross escribió:
> 
> 1.  Install the Password Exporter extension.  Since the "vanilla"
> version is not compatible with SeaMonkey, I am uploading my converted
> version to my Web site.  It is at
> .  (I will
> remove it from my Web site in two weeks.)
> (...)

Thank you very much. I've downloaded it and use it to follow your steps.

But, since I had the exported passwords and a full profile backup, I
dared to upgrade WITHOUT first removing the master password...

And guess what! Everything worked OK! I tested a number of saved
passwords in different websites, until I got tired of being successful
in every try. The email accounts work fine, too, and I have some X.509
certificates that also worked OK.

Still, I do not endorse anyone to do the same than me; if you do, be
absolutely sure that you have a good, complete backup of your profile
(and, if you have more than one profile, remember to follow steps for
each one).


> If you cannot import your passwords without first establishing a master
> password, then you have a version of SeaMonkey that has been tailored to
> meet FIPS security requirements.  (FIPS means "federal information
> processing statndards" and is imposed on government and government
> contractor computer installations.)


I'm using official builds of SeaMonkey, but my profile may be dated
back to 1995, when I started using Netscape as my email agent. It was
created on Windows 3.11 and ported to Linux some years after that. I'm
definitely using this profile on Linux with Mozilla Suite since, at
least, 2002. Could it be that the FIPS tail comes from that old ages?

Thanks a lot for all your help.

-- 
Proyecto NAVE (Mozilla es-ES Localization Team)
Mozilla Hispano Community

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: No empty master password allowed in FIPS Software Security Device

2020-03-07 Thread Ricardo Palomares Martí­nez
El 6/3/20 a las 6:37, jcteyssi...@gmail.com escribió:
> 
> One idea: just replace linux's profile (after abckup of course) with win 10's 
> one since mastrer password deleted?
> 


Profiles in Linux and Windows are different, so I can't do that. :-)
Actually, the Windows 10 profile is a very basic one (no email
accounts, for instance) with just one saved password added to test the
procedure.

Thanks anyway. In my reply to David E. Ross I explain the (surprising)
outcome of my story.

-- 
Proyecto NAVE (Mozilla es-ES Localization Team)
Mozilla Hispano Community

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Is there a way to know which extensions may break when upgrading?

2020-03-07 Thread Steve Dunn

On 2020-03-06 18:09, Ant wrote:

You could share what extensions you have and we can tell you. Here's mine:


The most important ones for me are:

* JunQuilla 1.0.4
* Adblock Plus 2.9.1 (which the 2.53.1 release notes say is problematic, 
but someone else in this thread is also using)

* HTTPS Everywhere 5.2.20

	I stopped using SeaMonkey for most browsing a couple of years ago - 
Firefox is so much faster, has fewer sites that refuse to work with it, 
gets security updates much more promptly, and doesn't have to rely on 
obsolete extensions.  I mostly use SeaMonkey for email and newsgroups, 
and if some of my other extensions break, I can deal with it.


-Steve
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: How to build 2.53.1 on FreeBSD ?

2020-03-07 Thread BERTRAND Joël
Some news.

I don't know why -DWEBRTC_POSIX -DWEBRTC_BUILD_LIBEVENT -DWEBRTC_BSD
-DWEBRTC_NS_FLOAT are not set under FreeBSD. Thus I have added these
options in mozilla/config/rules.mk

Compilation continues until link stage that aborts with :

/usr/bin/ld: error: undefined symbol: arc4random_addrandom
>>> referenced by evutil_rand.c:199
(/root/seamonkey/seamonkey-2.53.1/mozilla/ipc/chromium/src/third_party/libevent/evutil_rand.c:199)
>>>
../../ipc/chromium/src/third_party/Unified_c_src_third_party0.o:(evutil_secure_rng_add_bytes)

/usr/bin/ld: error: undefined symbol:
webrtc::DesktopCaptureImpl::CreateDeviceInfo(int, webrtc::CaptureDeviceType)
>>> referenced by VideoEngine.cpp:140
(/root/seamonkey/seamonkey-2.53.1/mozilla/dom/media/systemservices/VideoEngine.cpp:140)
>>>
../../dom/media/systemservices/Unified_cpp_systemservices0.o:(mozilla::camera::VideoEngine::GetOrCreateVideoCaptureDeviceInfo())

/usr/bin/ld: error: undefined symbol:
webrtc::DesktopCaptureImpl::Create(int, char const*,
webrtc::CaptureDeviceType)
>>> referenced by VideoEngine.cpp:60
(/root/seamonkey/seamonkey-2.53.1/mozilla/dom/media/systemservices/VideoEngine.cpp:60)
>>>
../../dom/media/systemservices/Unified_cpp_systemservices0.o:(mozilla::media::LambdaRunnable::Run())

/usr/bin/ld: error: undefined symbol: webrtc::Atomic32::operator+=(int)
>>> referenced by atomic32.h:45
(/root/seamonkey/seamonkey-2.53.1/mozilla/media/webrtc/trunk/webrtc/system_wrappers/include/atomic32.h:45)
>>>
../../dom/media/webrtc/Unified_cpp_dom_media_webrtc0.o:(mozilla::AudioOutputObserver::~AudioOutputObserver())

/usr/bin/ld: error: undefined symbol: webrtc::Atomic32::operator+=(int)
>>> referenced by atomic32.h:45
(/root/seamonkey/seamonkey-2.53.1/mozilla/media/webrtc/trunk/webrtc/system_wrappers/include/atomic32.h:45)
>>>
../../dom/media/webrtc/Unified_cpp_dom_media_webrtc0.o:(mozilla::AudioOutputObserver::Clear())

/usr/bin/ld: error: undefined symbol: webrtc::Atomic32::operator+=(int)
>>> referenced by atomic32.h:45
(/root/seamonkey/seamonkey-2.53.1/mozilla/media/webrtc/trunk/webrtc/system_wrappers/include/atomic32.h:45)
>>>
../../dom/media/webrtc/Unified_cpp_dom_media_webrtc0.o:(mozilla::AudioOutputObserver::Size())
...


I have seen that arc4random_addrandom was deprecated on FreeBSD. Thus,
I have tried to build seamonkey with ac_add_options
--with-system-libevent but I'm obtain the same result...

Any idea to fix this issue ?

Best regards,

JB
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Is there a way to know which extensions may break when upgrading?

2020-03-07 Thread Jonathan N. Little
Jonathan N. Little wrote:
> Extensions were not a issue, it was *plugins* where the real winnowing
> occurred. I had to add "PDF Viewer" to replace my lost Nitro PDF viewer
> plugin.

Oh and now Netflix does not work now, (Silverlight plugin maybe?),
except this is ONLY on my Windows 10 desktop. It works just fine on
Linux with SeaMonkey v2.53.1 for some strange reason.

-- 
Take care,

Jonathan
---
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Is there a way to know which extensions may break when upgrading?

2020-03-07 Thread Jonathan N. Little
 Mr. Ed  wrote:
> On 3/6/2020 6:09 PM, Ant wrote:
>> On 3/6/2020 2:37 PM, Steve Dunn wrote:
>>>  There seems to be a fair bit of potential for extensions that
>>> work in 2.49.x to break in 2.53.1, based on what people have been
>>> posting here. I can't say I'm surprised, given that the developers
>>> have to try to maintain compatibility with an obsolete extension
>>> system while grafting in components from a browser that moved to a
>>> modern extension system a few years ago, but since extensions are
>>> important, it's kind of a problem if the stop working.
>>>
>>>  Is there a way to know for sure which of your favourite
>>> extensions will work in 2.53.1, or is it a case of back up, hope for
>>> the best, and be prepared to uninstall 2.53.1, reinstall 2.49.5, and
>>> restore your backup?
>>
>> You could share what extensions you have and we can tell you. Here's
>> mine:
>>
>> Last updated: Fri Mar 06 2020 15:08:50 GMT-0800 (Pacific Standard Time)
>> User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0)
>> Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.1
>>
>> Extensions (enabled: 6)
>> * ColorfulTabs 31.1.9 (http://www.addongenie.com/colorfultabs)
>> * DOM Inspector 2.0.17.2 (http://www.mozilla.org/projects/inspector/)
>> * Expire history by days [converted] 1.2.0
>> * Open With 6.8.6 (https://github.com/darktrojan/openwith)
>> * PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)
>> * uBlock Origin 1.16.4.19
>> (https://github.com/gorhill/uBlock-for-firefox-legacy)
> 
> And mine:
> 
> User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0)
> Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.2
> 
> Extensions (enabled: 8)
> * English United States Dictionary 60.1webext
> * Enigmail 2.0.9 (https://www.enigmail.net/)
> * Mail Redirect 0.10.7 (https://mailredirect.sourceforge.io/)
> * NetVideoHunter [converted] 1.20 (http://www.netvideohunter.com) (disabled)
> * Password Exporter Converted 1.3.4 (http://passwordexporter.fligtar.com)
> * PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)
> * Quote Colors 0.3.1-let-fixed (http://quotecolors.mozdev.org/)
> * Reply to All as Cc [converted] 1.5.1 (http://www.clear-code.com/)
> * Saved Password Editor 2.9.6 
> (https://addons.mozilla.org/addon/saved-password-editor/)
> 

And mine

User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
Firefox/60.0 SeaMonkey/2.53.1

* Adblock Plus  2.9.1
* ChatZilla 0.9.94
* Classic Password Editor   1.0.3
* DOM Inspector 2.0.17.2
* Enigmail  2.0.9
* Font Information  0.1
* JavaScript Debugger   0.9.89.1-signed.1-signed
* Lightning 5.8.1
* Mnenhy0.8.6.1.2-stanio
* PDF Viewer2.2.255
* ReminderFox   2.1.6.3
* SeaTab X 20.3.3
* Toggle JavaScript Button  1.1.1
* True Full Screen in SeaMonkey 1.1.5
* Web Developer 1.2.13

Extensions were not a issue, it was *plugins* where the real winnowing
occurred. I had to add "PDF Viewer" to replace my lost Nitro PDF viewer
plugin.

-- 
Take care,

Jonathan
---
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Mail Folders Not Showing With SM 2.51.3 Win 10 Pro v. 1909

2020-03-07 Thread bo1953
On Friday, March 6, 2020 at 7:23:42 AM UTC-5, Frank-Rainer Grahl wrote:
> bo1953 wrote:
> > Hello all - when updating to SM 2.51.3 my mail folders disappear.,, when I 
> > click in the blank area I do see the emails in whichever folder it landed 
> > on.
> > 
> > I tried compacting the folders and deleting the msf files and this not help.
> > 
> > On my other W10 systems this has not happened at all.
> > 
> > Suggestions or ideas?
> > 
> > TIA bo1953
> > 
> 
> Extensions, themes or bad graphics drivers? Intel graphics by chance? 
> Anything 
> in the error log?
> 
> 
> FRG

FRG - Thank you for your response... To answer you questions...

Extensions used currently include:

Chatzilla
CookieKeeper
DOM Inspector
Manually sort folders
Sticky Password
uBlock Origin
User Agent Switcher

Plugins

Adobe Acrobat
Shockwave Flash
Silverlight
Sticky Password

The theme is standard with SM, without any modifications.

The videos drivers are current and were already up to date.

The graphics are Intel: Intel HD Graphics 530 and NVIDIA GeForce 940MX

How to find out where the error log is and copy it for review?

TIA - SamuelS3
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Sea monkey transfer to bigger tank

2020-03-07 Thread toby
Hi I have my sea monkeys in a mason jar (500ml). They are about one month old 
and more than 1 CM, but just 5 of them survived.

I would like to transfer them to a 1.5 litre mason jar but do not want to hurt 
them.

Below is my plan--is this is the right way?
Fill my 1.5 litre mason with 1 litre of bottled water. Add a packet of water 
purifier. Wait 24 hours. Add the 500ml along with the 5 sea monkeys from the 
existing 500ml mason jar. 

Then continue to feed them every few days with the small scoop of growth food. 

Is that correct?

Thank you,

Toby
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Is there a way to know which extensions may break when upgrading?

2020-03-07 Thread  Mr . Ed  via support-seamonkey

  
  
On 3/7/2020 12:21 AM, Ant wrote:

On
  3/6/2020 6:22 PM,  Mr. Ed  wrote:
  
  On 3/6/2020 6:09 PM, Ant wrote:

On 3/6/2020 2:37 PM, Steve Dunn wrote:
  
   There seems to be a fair bit of
potential for extensions that work in 2.49.x to break in
2.53.1, based on what people have been posting here. I can't
say I'm surprised, given that the developers have to try to
maintain compatibility with an obsolete extension system
while grafting in components from a browser that moved to a
modern extension system a few years ago, but since
extensions are important, it's kind of a problem if the stop
working.


 Is there a way to know for sure which of your favourite
extensions will work in 2.53.1, or is it a case of back up,
hope for the best, and be prepared to uninstall 2.53.1,
reinstall 2.49.5, and restore your backup?

  
  
  You could share what extensions you have and we can tell you.
  Here's mine:
  
  
  Last updated: Fri Mar 06 2020 15:08:50 GMT-0800 (Pacific
  Standard Time)
  
  User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0)
  Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.1
  
  
  Extensions (enabled: 6)
  
  * ColorfulTabs 31.1.9 (http://www.addongenie.com/colorfultabs)
  
  * DOM Inspector 2.0.17.2
  (http://www.mozilla.org/projects/inspector/)
  
  * Expire history by days [converted] 1.2.0
  
  * Open With 6.8.6 (https://github.com/darktrojan/openwith)
  
  * PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)
  
  * uBlock Origin 1.16.4.19
  (https://github.com/gorhill/uBlock-for-firefox-legacy)
  


And mine:


User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0)
Gecko/20100101

Firefox/60.0 SeaMonkey/2.53.2


Extensions (enabled: 8)

* English United States Dictionary 60.1webext

* Enigmail 2.0.9 (https://www.enigmail.net/)

* Mail Redirect 0.10.7 (https://mailredirect.sourceforge.io/)

* NetVideoHunter [converted] 1.20
(http://www.netvideohunter.com) (disabled)

* Password Exporter Converted 1.3.4
(http://passwordexporter.fligtar.com)

* PrefBar 7.1.1 (http://prefbar.tuxfamily.org/)

* Quote Colors 0.3.1-let-fixed (http://quotecolors.mozdev.org/)

* Reply to All as Cc [converted] 1.5.1
(http://www.clear-code.com/)

* Saved Password Editor 2.9.6
(https://addons.mozilla.org/addon/saved-password-editor/)

  
  
  No ad blocker, horsey? :/
  


Yeh, done by the usage of the Windows 'hosts' file:
http://someonewhocares.org/hosts/


-- 
"This is America!  You can't make a horse
 testify against himself!"  -Mister Ed
  

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.53.1's about:crashes' report ID link doesn't work.

2020-03-07 Thread Frank-Rainer Grahl

Ant wrote:

On 3/6/2020 12:16 PM, Yamo' wrote:

Hi,

Ant a tapoté le 06/03/2020 19:15:

Hello.

I just had my very first crash in v2.53.1 while opening a couple new web
site tabs. I shared my report and restarted SeaMonkey v2.53.1. I went to
its about:crashes web page, but its report ID link doesn't work and its
URL shows http://crash-stats.mozilla.com/about/throttling. Is anyone
else having this problem too if you shared your crash reports? :(

What's up? Thank you for reading and hopefully answering soon. :)



My about:crashes work. But my only crash with 2.53.1 is a little old :

 



Yeah, yours was submitted before v2.53.1. Here's mine:

Unsubmitted Crash Reports
Report ID Date Crashed
8f669dc0-7ed4-44c2-872d-5b4aa11dfd22
 3/6/2020    10:03 AM


Should work soon again. We and Thunderbird need to find a new crashserver home 
in August/September. It would have been nicce if someeone had told us before 
blocking anything above 2.49.5 but can't be helped.


https://bugzilla.mozilla.org/show_bug.cgi?id=1619101

When the bug is closed unsent crash reports can then be send if you 
doubleclick on them in about:crashes.


FRG
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: For those who use PrefBar v7.1.1, does its clone button not work anymore for you too?

2020-03-07 Thread Frank-Rainer Grahl

Ant wrote:
When I clone a loaded web page tab, I get a blank tab titled "Untitled". It 
used to work in SeaMonkey v2.49.5 and earlier versions in both my decade old 
64-bit W7 HPE SP1 and 12 years old Linux/Debian Jessie v8 PC. Maybe its code 
needs to be updated? :(


Thank you for reading and hopefully answering. :)


Between 52 and 56 security was enhanced. Probably needs a triggering principal 
for the url open. Needs to be done on the prefbar side in this case.


FRG
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey