SM v2.48's Print Preview's First Page and Last Page buttons...

https://i.cubeupload.com/NC2Fkm.gif for an example from my updated 64-bit W7 HPE SP1 box (see the print preview toolbar). Is anyone else seeing this too in theirs? I did not have this problem in v2.46 and earlier. Thank you in advance. :) -- "Busy as ants hurrying orcs were digging, digging

Re: SeaMonkey 2.48 released!

Yamo' wrote: Hi, David H. Durgee wrote on 7/31/17 6:35 PM: In that case, has anyone notified the maintainer of Ubuntuzilla that the official release of 2.48 is now available? I would like to get back to using that repository to update SeaMonkey as opposed to a manual install every time an

Re: SM 2.50???

If you don't want to become a Beta tester switch to 2.49.1 when it becomes available. 2.50 has some problems especially with mail. If they don't bother you stay on it for now. The codebase is at least newer than 2.48. 2.51 is the same. FRG Pat Connors wrote: I am also using 2.50.  Should I

Re: SM 2.50???

Thanks, Ray I have had no problems with 2.50, all of Adrian's versions have worked fine. Keep as many versions of SM on the HDD as you would like to try. Use the same profiles for each. When there is a version you no longer want, delete. Never get rid of something that works until you like

Re: SM 2.50???

Pat Connors wrote: I am also using 2.50. Should I continue with it or go install the 2.48? I am confused as usual. What is this 2.50 I have been using. I now don't even know where I got it. Keep as many versions of SM on the HDD as you would like to try. Use the same profiles for each.

Starting SM empties profile data files

HP Pavilion dv7 The as-shipped plus updates W7 home is on one partition. W7U is on another partition. The following SMs are on an apps partition. I started using 2.50 a few months ago. I just got 2.48 and am using it now. User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0)

Re: SM 2.50???

I am also using 2.50. Should I continue with it or go install the 2.48? I am confused as usual. What is this 2.50 I have been using. I now don't even know where I got it. -- Pat Connors http://www.connorsgenealogy.com ___ support-seamonkey

Re: SM 2.50???

On 04/08/2017 17:50, Ray Davison wrote: > What is this 2.50 I have been using. I now don't even know where I got it. > > You are currently on the release update channel. > Build identifier: 20170424091539 You probably got it from there:

Re: E MAIL CRASHES ON 2.48

> I jumped on the ESR as soon as Adrian published it. > The source code is ready, it just needs to be compiled. Nope. Just found out the OS X bug wasn't fixed for 52. TB took it into a branch. We need to do the same or maybe use the branch from the next TB which should be due soon. There

SM 2.50???

What is this 2.50 I have been using. I now don't even know where I got it. You are currently on the release update channel. Build identifier: 20170424091539 TY Ray ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org

Re: win64 contributed builds.

I'm running 2.53a1 (downloaded this afternoon), and I noticed that mail doesn't follow the HTML preference in a contact entry. I have to use Options to send the message in HTML. Frank-Rainer Grahl wrote: Got a late beta fix and is now working in 2.53+ 2.54 is broken right now. I wouldn't

Re: E MAIL CRASHES ON 2.48

On 04/08/2017 14:34, WaltS48 wrote: > On 8/4/17 3:06 AM, Mason83 wrote: >> On 04/08/2017 04:12, Edmund Wong wrote: >>> Frank-Rainer Grahl wrote: It is probably bug 1286613: https://bugzilla.mozilla.org/show_bug.cgi?id=1286613 Solution is unfortunately to go back to 2.46

Re: win64 contributed builds.

\o/ Looking forward to testing whenever it appears. Thanks for the update. Got a late beta fix and is now working in 2.53+ 2.54 is broken right now. I wouldn't touch it for a week at least. Need some time to fix up the tree. FRG TCW wrote: I reverted back to Adrian's 2.52 beta for now.

Re: SeaMonkey 2.48 released!

On 04/08/17 22:33, WaltS48 wrote: On 8/4/17 5:26 AM, Yamo' wrote: Hi, David H. Durgee wrote on 7/31/17 6:35 PM: In that case, has anyone notified the maintainer of Ubuntuzilla that the official release of 2.48 is now available? I would like to get back to using that repository to update

Re: E MAIL CRASHES ON 2.48

On 8/4/17 3:06 AM, Mason83 wrote: On 04/08/2017 04:12, Edmund Wong wrote: Frank-Rainer Grahl wrote: It is probably bug 1286613: https://bugzilla.mozilla.org/show_bug.cgi?id=1286613 Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not sure if we can backport all the parts to

Re: SeaMonkey 2.48 released!

On 8/4/17 5:26 AM, Yamo' wrote: Hi, David H. Durgee wrote on 7/31/17 6:35 PM: In that case, has anyone notified the maintainer of Ubuntuzilla that the official release of 2.48 is now available? I would like to get back to using that repository to update SeaMonkey as opposed to a manual

Re: Cannot contact my router.

On Thursday, August 3, 2017 at 8:54:49 PM UTC-5, marks...@sbcglobal.net wrote: > Just updated to 2.48 a few minutes ago. Now I cannot contact my router at > 192.168.11 anymore. I get a red error screen saying...401 Authorization > Required > This server could not verify that you are

Re: SeaMonkey 2.48 released!

Hi, David H. Durgee wrote on 7/31/17 6:35 PM: > In that case, has anyone notified the maintainer of Ubuntuzilla that the > official release of 2.48 is now available? I would like to get back to > using that repository to update SeaMonkey as opposed to a manual install > every time an update

Re: FF 57 Changes and SeaMonkey

Paul Bergsagel writes: > Hi, > > I am wondering how all the new changes to FF57 will effect SeaMonkey? > > Will most of the changes be to the rendering engine, Gecko (or whatever the > new rendering engine will be called). Will we see a lot of new changes to how > we as end

Re: E MAIL CRASHES ON 2.48

On 04/08/2017 04:12, Edmund Wong wrote: > Frank-Rainer Grahl wrote: >> It is probably bug 1286613: >> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1286613 >> >> Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not >> sure if we can backport all the parts to 2.48 and do a 2.48.1

Re: Cannot contact my router.

On 04/08/2017 03:54, marksattler wrote: > Just updated to 2.48 a few minutes ago. Now I cannot contact my > router at 192.168.11 anymore. I get a red error screen > saying...401 Authorization Required > > This server could not verify that you are authorized to access. > Either you supplied