Re: SM 2.46 vs 2.50a1 nightly on OS X

The bug which tracks the underlying SeaMonkey changes is: https://bugzilla.mozilla.org/show_bug.cgi?id=1323494 All themes likely might need some changes too. FRG John Duncan wrote: John Duncan wrote: http://i.imgur.com/emcJad6.png Okay, so both the webaudio and add-on install popup

Re: SM 2.46 vs 2.50a1 nightly on OS X

John Duncan wrote: John Duncan wrote: Frank-Rainer Grahl wrote: John Duncan wrote: John Duncan wrote: Frank-Rainer Grahl wrote: followup error from the above. Is it? Seems unrelated to the aArguments error, but maybe I'm missing something. Should go away in a new build. Didn't look

Re: SM 2.46 vs 2.50a1 nightly on OS X

John Duncan wrote: Frank-Rainer Grahl wrote: John Duncan wrote: John Duncan wrote: Frank-Rainer Grahl wrote: followup error from the above. Is it? Seems unrelated to the aArguments error, but maybe I'm missing something. Should go away in a new build. Didn't look into it too hard but

Re: SM 2.46 vs 2.50a1 nightly on OS X

Frank-Rainer Grahl wrote: John Duncan wrote: John Duncan wrote: Frank-Rainer Grahl wrote: followup error from the above. Is it? Seems unrelated to the aArguments error, but maybe I'm missing something. Should go away in a new build. Didn't look into it too hard but something was not set

Re: SM 2.46 vs 2.50a1 nightly on OS X

You are right with the tabinfo too. My memory failed me. There were a bunch of follow up errors from the first fixed tabbrowser.xml error. FRG John Duncan wrote: The 'tabinfo is undefined error' still happens when you first open the mailnews window, and the 'browsers[i] is undefined error'

Re: SM 2.46 vs 2.50a1 nightly on OS X

John Duncan wrote: John Duncan wrote: Frank-Rainer Grahl wrote: followup error from the above. Is it? Seems unrelated to the aArguments error, but maybe I'm missing something. Should go away in a new build. Didn't look into it too hard but something was not set because of the previous

Re: SM 2.46 vs 2.50a1 nightly on OS X

John Duncan wrote: Frank-Rainer Grahl wrote: John Duncan wrote: 2.50 seems to be running much better than 2.46 release, from what I can tell. Try 2.49a2 instead. It will be the next ESR release and probably will become the standard release till 2018. Worst case it might also be the last

Re: SM 2.46 vs 2.50a1 nightly on OS X

Frank-Rainer Grahl wrote: John Duncan wrote: 2.50 seems to be running much better than 2.46 release, from what I can tell. Try 2.49a2 instead. It will be the next ESR release and probably will become the standard release till 2018. Worst case it might also be the last one if the XUL and

Re: SM 2.46 vs 2.50a1 nightly on OS X

buildbot gremlins. Likely because gcc got bumped to 4.9 or some other required package update. Ewong was busy with 2.46. Should be resolved in the next days. Tinderbox-builds are still available. https://archive.mozilla.org/pub/seamonkey/tinderbox-builds/comm-aurora-linux64/ WaltS48 wrote:

Re: SM 2.46 vs 2.50a1 nightly on OS X

On 12/25/2016 06:52 AM, Frank-Rainer Grahl wrote: Try 2.49a2 instead. Why is the latest build for Linux dated 18-Dec-2016? -- Visit Pittsburgh Coexist National Popular Vote 2,864,974 more than

Re: SM 2.46 vs 2.50a1 nightly on OS X

John Duncan wrote: 2.50 seems to be running much better than 2.46 release, from what I can tell. Try 2.49a2 instead. It will be the next ESR release and probably will become the standard release till 2018. Worst case it might also be the last one if the XUL and XPI deprecation goes thru as

Re: SM 2.46 vs 2.50a1 nightly on OS X

John Duncan wrote: 2.50 seems to be running much better than 2.46 release, from what I can tell. I have had big problems over the past couple of days with 2.46, wherein each time I loaded a web page, CPU usage would jump to 100% and last 2-3 seconds after the page had finished loading.

SM 2.46 vs 2.50a1 nightly on OS X

2.50 seems to be running much better than 2.46 release, from what I can tell. I have had big problems over the past couple of days with 2.46, wherein each time I loaded a web page, CPU usage would jump to 100% and last 2-3 seconds after the page had finished loading. Deleting places.sqlite