Re: new 2.48 available

On 2/5/2017 at 3:58 PM, EE's prodigious digits fired off with great aplomb: Ray Davison wrote: Bret Busby wrote: what is the command to show the version number that is installed, without having to load the application? Can you run SM? Does "Help" appear at the top of the SM window? If you

Re: new 2.48 available

EE wrote on 05-02-17 21:58: Ray Davison wrote: Bret Busby wrote: what is the command to show the version number that is installed, without having to load the application? Can you run SM? Does "Help" appear at the top of the SM window? If you click it does that produce a drop down that

Re: new 2.48 available

Ray Davison wrote: Bret Busby wrote: what is the command to show the version number that is installed, without having to load the application? Can you run SM? Does "Help" appear at the top of the SM window? If you click it does that produce a drop down that includes "About SM"? If you click

Re: new 2.48 available

On 05/02/2017, Ray Davison wrote: > Bret Busby wrote: >> what is the command to show the version number >> that is installed, without having to load the application? > > Can you run SM? > Does "Help" appear at the top of the SM window? > If you click it does that produce a

Re: new 2.48 available

Bret Busby wrote: what is the command to show the version number that is installed, without having to load the application? Can you run SM? Does "Help" appear at the top of the SM window? If you click it does that produce a drop down that includes "About SM"? If you click that does it yield

Re: new 2.48 available

On 01/29/2017 04:31 PM, Pat Connors wrote: I have been using 2.47 without any problems, and I see this (2.48) is not on the SeaMonkey website, so is it not authorized as is the 2.47 I am using? Is there a good reason why I should switch when I have no problems with my 2.47? I've been

Re: new 2.48 available

J. Weaver Jr. wrote: My 2.48 came as an automatic update to the 2.47 I was using. I've noticed one bug so far: the default button (usually "OK") on most dialogs is active and functional, but _visually_ "greyed out", with the legend just barely visible. -JW Seems to be a problem with the

Re: new 2.48 available

The sad truth is that until more people actively contribute this won't change e.g. has a fairly low priority. Basically pick the minor version number add 3 and look up the corresponding Firefox release notes. For 2.46 the fix for the just discovered zero day vulnerability was backported. FRG

Re: new 2.48 available

Hi, NoOp a écrit le 31/01/2017 à 22:25 : > Security information is still on 2.38: > > I didn't found a bug report ; I've reported a new one. -- Sorry for possible mistakes in English! http://pasdenom.info/

Re: new 2.48 available

On 1/31/2017 2:14 PM, Frank-Rainer Grahl wrote: > Ok and bye. > > FRG Right... It would be *very* helpful if you can advise which one of these fixed bugs address the comparable CVE/security fixes on Firefox and Thunderbird:

Re: new 2.48 available

Ok and bye. FRG NoOp wrote: I never thought I'd do this, but I'm actually now starting to tweak Thundebird UI/Themes so I can use on a full time basis, and using alternative browsers for the same. I've had to switch all of my clients from SeaMonkey as we are stuck in time with regards to

Re: new 2.48 available

On 1/31/2017 12:53 AM, Frank-Rainer Grahl wrote: > Its about:buildconfig in SeaMonkey and Firefox. > > But this only gives you the changelog for the whole source tree including > Thunderbird. > > FRG Correct. Of course you can compare against the 2.47 build:

Re: new 2.48 available

On 1/31/2017 12:26 AM, Daniel wrote: > On 31/01/2017 8:46 AM, NoOp wrote: >> On 01/30/2017 09:17 AM, Pat Connors wrote: >>> Thank you so much, yes, I do us 64 bit. While I am asking questions, >>> does anyone know if there is a place where I can read the changes in >>> this 2.48 version over the

Re: new 2.48 available

On 31/01/2017, Daniel wrote: > On 30/01/2017 6:06 PM, Bret Busby wrote: >> On 30/01/2017, WaltS48 wrote: >>> On 01/29/2017 06:31 PM, Pat Connors wrote: I have been using 2.47 without any problems, and I see this (2.48) is not on the

Re: new 2.48 available

Its about:buildconfig in SeaMonkey and Firefox. But this only gives you the changelog for the whole source tree including Thunderbird. FRG Daniel wrote: ... Clicking on your about:build gets "Invalid Address The URL is not valid and cannot be loaded. The provided address is not in

Re: new 2.48 available

On 31/01/2017 8:46 AM, NoOp wrote: On 01/30/2017 09:17 AM, Pat Connors wrote: Thank you so much, yes, I do us 64 bit. While I am asking questions, does anyone know if there is a place where I can read the changes in this 2.48 version over the 2.47 version. change to ...-windows64/ if you use

Re: new 2.48 available

On 31/01/2017 12:19 AM, Lee wrote: On 1/30/17, me wrote: Pat Connors wrote: I have been using 2.47 without any problems, and I see this (2.48) is not on the SeaMonkey website, so is it not authorized as is the 2.47 I am using? Is there a good reason why I should switch when

Re: new 2.48 available

On 30/01/2017 6:06 PM, Bret Busby wrote: On 30/01/2017, WaltS48 wrote: On 01/29/2017 06:31 PM, Pat Connors wrote: I have been using 2.47 without any problems, and I see this (2.48) is not on the SeaMonkey website, so is it not authorized as is the 2.47 I am using?

Re: new 2.48 available

TCW wrote: > On Sun, 29 Jan 2017 15:31:23 -0800, Pat Connors > wrote: > >> I have been using 2.47 without any problems, and I see this (2.48) is >> not on the SeaMonkey website, so is it not authorized as is the 2.47 I >> am using? Is there a good reason why I should

Re: new 2.48 available

On 01/30/2017 09:17 AM, Pat Connors wrote: > Thank you so much, yes, I do us 64 bit. While I am asking questions, > does anyone know if there is a place where I can read the changes in > this 2.48 version over the 2.47 version. > >> change to ...-windows64/ if you use 64-bit. > >

Re: new 2.48 available

On 01/30/2017 02:06 AM, Bret Busby wrote: On 30/01/2017, WaltS48 wrote: On 01/29/2017 06:31 PM, Pat Connors wrote: I have been using 2.47 without any problems, and I see this (2.48) is not on the SeaMonkey website, so is it not authorized as is the 2.47 I am using?

Re: new 2.48 available

Mostly boring stuff under the hood compared to the jump from 2.40 to 2.46. Ratty fixed the default search engine setting which caused so much noise. You can generate and up to date list of fixes for SeaMonkey in the status meeting notes:

Re: new 2.48 available

Pat Connors wrote: I have been using 2.47 without any problems, and I see this (2.48) is not on the SeaMonkey website, so is it not authorized as is the 2.47 I am using? Is there a good reason why I should switch when I have no problems with my 2.47? Who said you had to switch? 2.46 is the

Re: new 2.48 available

On 1/30/2017 11:17 AM, Pat Connors wrote: Thank you so much, yes, I do us 64 bit. While I am asking questions, does anyone know if there is a place where I can read the changes in this 2.48 version over the 2.47 version. change to ...-windows64/ if you use 64-bit. It's basically Firefox

Re: new 2.48 available

Thank you so much, yes, I do us 64 bit. While I am asking questions, does anyone know if there is a place where I can read the changes in this 2.48 version over the 2.47 version. change to ...-windows64/ if you use 64-bit. -- Pat Connors http://www.connorsgenealogy.com

Re: new 2.48 available

On 1/30/2017 10:25 AM, Pat Connors wrote: I have been using 2.47 without any problems, and I see this (2.48) is not on the SeaMonkey website, so is it not authorized as is the 2.47 I am using? Is there a good reason why I should switch when I have no problems with my 2.47? I think you

Re: new 2.48 available

My 2.48 came as an automatic update to the 2.47 I was using. I've noticed one bug so far: the default button (usually "OK") on most dialogs is active and functional, but _visually_ "greyed out", with the legend just barely visible. -JW ___

Re: new 2.48 available

I have been using 2.47 without any problems, and I see this (2.48) is not on the SeaMonkey website, so is it not authorized as is the 2.47 I am using? Is there a good reason why I should switch when I have no problems with my 2.47? I think you should be certain where your browser came from.

Re: new 2.48 available

On 01/30/2017 02:06 AM, Bret Busby wrote: On 30/01/2017, WaltS48 wrote: On 01/29/2017 06:31 PM, Pat Connors wrote: I have been using 2.47 without any problems, and I see this (2.48) is not on the SeaMonkey website, so is it not authorized as is the 2.47 I am using?

Re: new 2.48 available

On 1/30/17, me wrote: > Pat Connors wrote: >> I have been using 2.47 without any problems, and I see this (2.48) is >> not on the SeaMonkey website, so is it not authorized as is the 2.47 I >> am using? Is there a good reason why I should switch when I have no >> problems with

Re: new 2.48 available

Pat Connors wrote: > I have been using 2.47 without any problems, and I see this (2.48) is > not on the SeaMonkey website, so is it not authorized as is the 2.47 I > am using? Is there a good reason why I should switch when I have no > problems with my 2.47? > I think you should be certain

Re: new 2.48 available

On 30/01/2017, WaltS48 wrote: > On 01/29/2017 06:31 PM, Pat Connors wrote: >> I have been using 2.47 without any problems, and I see this (2.48) is >> not on the SeaMonkey website, so is it not authorized as is the 2.47 I >> am using? Is there a good reason why I should

Re: new 2.48 available

WaltS48 a écrit le 30/01/2017 à 01:19 : > On 01/29/2017 06:31 PM, Pat Connors wrote: >> I have been using 2.47 without any problems, and I see this (2.48) is >> not on the SeaMonkey website, so is it not authorized as is the 2.47 I >> am using? Is there a good reason why I should switch when I

Re: new 2.48 available

On 01/29/2017 06:31 PM, Pat Connors wrote: I have been using 2.47 without any problems, and I see this (2.48) is not on the SeaMonkey website, so is it not authorized as is the 2.47 I am using? Is there a good reason why I should switch when I have no problems with my 2.47? There is no

new 2.48 available

I have been using 2.47 without any problems, and I see this (2.48) is not on the SeaMonkey website, so is it not authorized as is the 2.47 I am using? Is there a good reason why I should switch when I have no problems with my 2.47? -- Pat Connors http://www.connorsgenealogy.com