Re: SeaMonkey v2.49.1 is out!

[John Duncan]

Ant wrote:

Well almost!

https://blog.seamonkey-project.org/2017/11/04/2-49-1-is-out/
https://blog.seamonkey-project.org/2017/11/04/404-error/

Maybe more in https://blog.seamonkey-project.org/ soon.
Great release! Getting strange CPU spikes when opening 
javascript-intense pages. Also, after a few hours of browsing, my GPU 
use spikes to over 40% as well. I somewhat remember running into these 
problems in a Firefox nightly awhile ago, so perhaps this is just some 
holdover bug from back then. Will test against 2.49 tomorrow to make 
sure that this was not always the case. Win10 x86.

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

Re: "Authentication Failed" When Retrieving eMail, SM 2.48, W10 Pro 64

[John Duncan]

Bo1953 wrote:

Hello all,

Having challenges retrieving emails into SM 2.48.

The error message is as follows:

Sending of password for user x...@techson.net did not succeed. Mail
server beast.noc.com responded: Authentication failed.

Is this a server side error or SM error? I can retrieve email via the
web portal.

TIA - bo1953
This could be due to an incorrectly entered password on your end. Have 
you recently changed the password for the account?

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

Re: Cannot access microsoft support page

[John Duncan]

Ray_Net wrote:

The page:
https://support.microsoft.com/en-ie/help/4038788/windows-10-update-kb4038788


Is OK when I use Internet-Explorer.

But when I use SM I got: Unresponsive script  with the following info:
A script on this page may be busy, or it may have stopped responding.
You can stop the script now, open the script in the debugger, or let the
script continue.
Script: https://support.microsoft.com/…7cAHzfyTrsysvfGBLWbje_0mtKHd81:128

Works for me on SM 2.48 (W10 x86_64). Does it help if you restart the 
browser?


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

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[John Duncan]

Frank-Rainer Grahl wrote:
They still have a lot of money to burn. Market share in 5 to 6 months 
should show if it is a success. I have my doubts. If you p*ss off enough 
power users who recommend it to others not much left. "Normal" users 
will just continue using Chrome. They don't care about privacy and all 
the other things Mozilla is touting as achievements for 57.
Totally agree. We shall see what is left of the FF user-base once the 
dust settles.


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

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[John Duncan]

WaltS48 wrote:

On 9/10/17 11:04 AM, Frank-Rainer Grahl wrote:
I probably need to do a Fx Nightly again just to see what changed but 
this is all so much urgkkk for only fanboys to love. This is all 
rushed and I personally hope it backfires but even this would do 
SeaMonkey no good.


Do you really call Photon and Quantum development over version 55, 56 
and 57 nighties, and 57 betas rushed?


When I first saw Australis, I went wtf?, then working with it over a 
series of Nightlies, I learned how to customize and use it.


Sure about 500,000 users installed CTR, but what percentage of total 
Firefox users is that.


When I first saw Photon in Fx 55.0, I went wtf?, where did my Menu 
Button icons go!. Now working with Photon over a series of Nightlies 
I've learned how to customize and use it.


Do I like all the changes. Not really, but clicking the Library button 
and having access to Bookmarks, Pocket List, History, Synced Tabs, 
Screenshots and Downloads is nice.


Call me fanboy if you like. Somebody has to counter the doom and gloom 
of the whiners.


The seemingly arbitrary and heavily bureaucratic decimation of a large 
number of older APIs and core features that power users depend on (in 
Mozilla's desperate bid to stay relevant in a world dominated by people 
who get flustered when the homepage of google tells them to download and 
install a new browser for an enhanced browsing experience) is more of 
the issue in this case.


Ignoring the random changes in Firefox's UI over the years, most of 
which are ignorable and/or inconsequential, there has been a troubling 
trend recently of an arbitrary reduction and deprecation of many 
different parts of the mozilla-central tree (you can't even keep history 
longer than like six months without yielding to extension fodder! 
They're removing 10+ years of work from add-on developers under the 
guise of techno-'modernity' and 'safety').


I am not saying that our community has all of the answers to these 
problems (the largest, imo, is a socio-cultural norm established by 
Google that socializes users in such a way as to passively accept a 
heavily simplified browsing experience, leading to a much smaller 
community of 'hackers'/power-users (which was, in comparison, fostered 
by orgs like Netscape/old Mozilla/etc.) thus causing other 
projects/organizations to follow suite to gain back the user-base that 
they lose).


Anyway, complaining about this probably won't really change any of the 
decisions coming from Mozilla, so for the foreseeable future, we'll just 
need to continuously re-build from the pieces that are left after the 
insanity of the Firefox 57 release dissipates.


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

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[John Duncan]

> Download Manager e.g. needs a serious makeover before I would want it to
> be released. This is more a case study since 2.52 :)
Right, I keep forgetting that the C++ download manager is being retired.
> I am still on 2.53. Didn't check if DOMi and cZ still work but if not
> they could surely being patched up. But Adblock+ and uBlock are both
> broken.
Right, with those moving toward pure web-extensions, I suppose SM will 
need to land web-extension support to properly run their most recent 
versions.

> We switched to ESR so that we have more time to prepare a release.
> Unless 4 to 5 programmers pop up it is unlikely then we will return the
> do releases from the release repo. After the 52 ESR branch is eol we
> plan to switch to ESR 59 for 2.56.x. If nad when it comes to that is
> still unsure if Mozilla continues to destroy the old codebase. We need
> to port Web Extension support and e10s at least for later releases but
> this is a huge task for such a small team.
Totally agree. That sounds like a relatively gargantuan undertaking for 
the tiny council/SM team.

>
> I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is
> unusable right now. Uninstalled all Fx 56/57 betas and nightlies and
> switched to esr 52 for testing only. I probably need to do a Fx Nightly
> again just to see what changed but this is all so much urgkkk for only
> fanboys to love. This is all rushed and I personally hope it backfires
> but even this would do SeaMonkey no good.
Cool. I will try out 2.53 then, as there is a noticeable speed 
difference (especially javascript) between the current FF nightly and SM 
2.48.
It all does seem extremely rushed and unprofessional; perhaps Mozilla 
has finally lost their way. I swear the only thing people on /r/Firefox 
talk about is the current Nightly icon change and other trivial and/or 
unimportant minor browser features (theming userChrome.css, etc.) If 
things do not go well with the 57 release, it really could be corporate 
suicide from Mozilla.

>
> Building 2.49.1 should atart soon. Everything has been checked in now. A
> little late but we do what we can with the limited resourced at hand.
No rush. The fact that the team gets such a great deal done with so 
little resources is a considerable achievement.


-john

Frank-Rainer Grahl wrote:

Forgive me if I have misunderstood the meeting minutes, but since the

nightly

release channel will continue to support things like XUL overlays, legacy
extensions, webextension eperiments, etc. [0], why don't you continue to
ingest & build off of mozilla-central?


Nightlies will, of course be build. The list of bug which needs to be
fixed before a SeaMonkey 2.54 would be usable is quite long and I didn't
even file one or two for bookmark and other problems yet:

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

Download Manager e.g. needs a serious makeover before I would want it to
be released. This is more a case study since 2.52 :)


Is the plan to eventually switch back from ESR once bug fixes are

landed and

the API removal spree has subsided? Or will the API changes break more
essential SeaMonkey features as well? It seems as if DOM
Inspector/Lightning/Chatzilla all still seem to be working in current

2.54

builds, which is a good sign.


I am still on 2.53. Didn't check if DOMi and cZ still work but if not
they could surely being patched up. But Adblock+ and uBlock are both
broken.

We switched to ESR so that we have more time to prepare a release.
Unless 4 to 5 programmers pop up it is unlikely then we will return the
do releases from the release repo. After the 52 ESR branch is eol we
plan to switch to ESR 59 for 2.56.x. If nad when it comes to that is
still unsure if Mozilla continues to destroy the old codebase. We need
to port Web Extension support and e10s at least for later releases but
this is a huge task for such a small team.

I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is
unusable right now. Uninstalled all Fx 56/57 betas and nightlies and
switched to esr 52 for testing only. I probably need to do a Fx Nightly
again just to see what changed but this is all so much urgkkk for only
fanboys to love. This is all rushed and I personally hope it backfires
but even this would do SeaMonkey no good.

Building 2.49.1 should atart soon. Everything has been checked in now. A
little late but we do what we can with the limited resourced at hand.

FRG

John Duncan wrote:

Frank-Rainer Grahl wrote:

I have a pacthes up 2.54 but it still needs at least two bugs fixed
before I would call it usable.

I am using a 2.53 with a few fixes still in review applied. If you want
it shoot me a mail Can bake any platform but Linux i686.

FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:

Before l10n.mozilla-community.org went down, I had the 2.52b x64
akalla built but it seems to be corrupt. Tried google

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[John Duncan]

Frank-Rainer Grahl wrote:

I have a pacthes up 2.54 but it still needs at least two bugs fixed
before I would call it usable.

I am using a 2.53 with a few fixes still in review applied. If you want
it shoot me a mail Can bake any platform but Linux i686.

FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:

Before l10n.mozilla-community.org went down, I had the 2.52b x64
akalla built but it seems to be corrupt. Tried google but nothing's
coming up. 2.51 is the newest I could fine. Anyone have the x64
2.52b build handy?


I have 2.53a1, but this newsgroup would not let me attach it because
it is over 72 MG. I think is the last nightly build that I
downloaded.  The only other 64-bit one that I have saved is 2.45.


That's all right. I know *some* movement on getting it back on a
hosting place is happening
(https://bugzilla.mozilla.org/show_bug.cgi?id=1383642) but it might be
a while. I was already playing with the 2.54a builds but the amount of
stuff busted in it is forcing me to revert back.
Saw those patches for 2.54. Glad you guys are staying sane during the 
Mozilla API decimation.


Forgive me if I have misunderstood the meeting minutes, but since the 
nightly release channel will continue to support things like XUL 
overlays, legacy extensions, webextension eperiments, etc. [0], why 
don't you continue to ingest & build off of mozilla-central?


Is the plan to eventually switch back from ESR once bug fixes are landed 
and the API removal spree has subsided? Or will the API changes break 
more essential SeaMonkey features as well? It seems as if DOM 
Inspector/Lightning/Chatzilla all still seem to be working in current 
2.54 builds, which is a good sign.


Total removal of complete themes could be a larger issue, though.

Thanks for your continued support.

[0]: https://wiki.mozilla.org/Add-ons/Firefox57
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM 2.46 and PDF file (Linux x86-64)

[John Duncan]

pconde wrote:

Thanks,

I checked  Firefox and its is the X86-64 version
"Architecture :x86_64
Package source :
MozillaFirefox-50.1.0-1.1
Media No. :1"

You are right that the Kpart  plugins is not activated in Firefox.
I didn't found in the plugins or extension of Firefox anything related 
to pdf.js.
Maybe this version of Firefox (From OpenSuse tumbleweed) contains the 
pdf.js?


I added the extension pdf.js in Seamonkey and It works now.
The look of this viewer is the same as in Firefox . So  I  assume that 
this extension
is also present in Firefox even is the component list of the RPM doesn't 
show it


Thanks for your help
Philippe

Frank-Rainer Grahl a écrit :

Plugings were blacklisted in recent x64 versions of Firefox and
SeaMonkey. You can try the i686 version. I am quite sure you are using a
i686 Firefox or it wouldn't work there too. Or it uses pdf.js the
internal pdf viewer there?

Only Flash and one or two others are whitelisted for now. All plugins
but Flash will go away in 2.50+ and Firefox 53.

FRG

pconde wrote:

Hello,

I have problem with PDF pages in Seamonkey 2.46: They are not more
displayed, I end with a grey page. In the preference ==> navigator ==>
application the only available option is "download file". I added an
external application (okular)  to display the PDF files but I prefer
to have the display in the browser;
With SM 2.40 the PDF page were displayed in the browser. ==> it was
using the Kparts plugin

In SM 2.46 the Kparts plugin is still available for other file types
but not for PDF.
If i use Firefox then the PDF files are displayed in the browser
(Firefox 50)

In the about:plugins for Seamonkey if find the Kpart plugin
"KParts Plugin
 File : libkpartsplugin.so
 Path : /home/philippe/.mozilla/plugins/libkpartsplugin.so
 Version :
 State : Enabled
 File viewer using KDE's KParts technology (2011-08-23)"

+/- 80 lines are displayed but nothing for PDF

In the about:plugins for Firefox I have
"KParts Plugin
 File: libkpartsplugin.so,libkpartsplugin.so
 Path:
/home/philippe/.mozilla/plugins/libkpartsplugin.so,/usr/lib64/browser-plugins/libkpartsplugin.so 



 Version:
 State: Enabled
 File viewer using KDE's KParts technology (2011-08-23)"

+/- 300 lines are displayed and there is one for PDF
"application/pdfPDF documentpdf"

the second path for Firefox "/usr/lib64/browser-plugins" contains the
same plugins that exist in the first path:
hpprol2:/usr/lib64/browser-plugins # ls -l  libkpartsplugin.so
-rwxr-xr-x 1 root root 114848 11 déc 01:19 libkpartsplugin.so

philippe@hpprol2:~/.mozilla/plugins> ls -l libkpartsplugin.so
-rwxr-xr-x 1 philippe users 114848 11 déc 01:19 libkpartsplugin.so

I tried in Seamonkey to set the plugin "ibkpartsplugin.so"  as
application for PDF but nothing is displayed
In Firefox if I set the plugin "ibkpartsplugin.so" as application for
PDF, the PDF is displayed

Any Idea from where this is coming?

  --
Regards
Philippe






pdf.js is built into firefox
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM 2.46 vs 2.50a1 nightly on OS X

[John Duncan]

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 into it too hard but 
something was not set because of the previous error.


So I tested this out in safe mode (with all add-ons) disabled, and the 
error seems to have disappeared. I will try going through each add-on 
to determine which one is causing this error.
- This has been an issue for awhile, but any time you click on an 
email or news message in mailnews, there is a type error in the 
'tabbrowser.xml' file


 Error: TypeError: browsers[i] is undefined
 Source File: chrome://navigator/content/tabbrowser.xml

The given line is: ``if (browsers[i].contentDocument == aDocument)"
(line 350)


followup error from the above.
But I thought this error has persisted at least since 2.40, and the 
errors above were only introduced in 2.50+




Sorry you are right. Do you use SeaTab X 2? I think its linked to it 
but not sure.
No, I do not. This error (browsers[i] is undefined] still persists 
even when I reboot into safe mode with all add-ons disabled, so I'm 
thinking it's perhaps unrelated to extensions? Once again, I could be 
wrong..


Yep, using the latest 2.50a1 tinderbox build (Dec. 25, build 
1482627108), all errors in the browser portion seem to be fixed. The 
workaround for installing addons seems to be working as well. It's 
styled a bit differently than on older versions, but seems to be 
functional.


http://i.imgur.com/5NlCHGt.png
http://i.imgur.com/VmA47K8.png

Yes the notifications changed. The needed CSS changes to 'deflat' it 
and make it more SeaMonkey friendly are not yet in.


Great. No worries; this is probably one of the nicest builds of SM 
I've ever used!


the webaudio interface seems a bit glitched as well, but works if you 
right click on it to play the content.


http://i.imgur.com/emcJad6.png
Okay, so both the webaudio and add-on install popup weirdness seem to be 
caused by my theme. I switched to the default one, and while they're 
still different than before (uglier imo, very modern/metro-y, not 
OS-specific like they used to be. I'm assuming the default OS-specific 
theme css has simply not been updated for these yet), they are at least 
better than the way my current theme is handling them.


http://i.imgur.com/kM12F4o.jpg
http://i.imgur.com/opw5KLb.jpg
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM 2.46 vs 2.50a1 nightly on OS X

[John Duncan]

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 
something was not set because of the previous error.


So I tested this out in safe mode (with all add-ons) disabled, and the 
error seems to have disappeared. I will try going through each add-on to 
determine which one is causing this error.
- This has been an issue for awhile, but any time you click on an 
email or news message in mailnews, there is a type error in the 
'tabbrowser.xml' file


 Error: TypeError: browsers[i] is undefined
 Source File: chrome://navigator/content/tabbrowser.xml

The given line is: ``if (browsers[i].contentDocument == aDocument)"
(line 350)


followup error from the above.
But I thought this error has persisted at least since 2.40, and the 
errors above were only introduced in 2.50+




Sorry you are right. Do you use SeaTab X 2? I think its linked to it 
but not sure.
No, I do not. This error (browsers[i] is undefined] still persists even 
when I reboot into safe mode with all add-ons disabled, so I'm thinking 
it's perhaps unrelated to extensions? Once again, I could be wrong..


Yep, using the latest 2.50a1 tinderbox build (Dec. 25, build 
1482627108), all errors in the browser portion seem to be fixed. The 
workaround for installing addons seems to be working as well. It's 
styled a bit differently than on older versions, but seems to be 
functional.


http://i.imgur.com/5NlCHGt.png
http://i.imgur.com/VmA47K8.png

Yes the notifications changed. The needed CSS changes to 'deflat' it 
and make it more SeaMonkey friendly are not yet in.


Great. No worries; this is probably one of the nicest builds of SM I've 
ever used!


the webaudio interface seems a bit glitched as well, but works if you 
right click on it to play the content.


http://i.imgur.com/emcJad6.png
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM 2.46 vs 2.50a1 nightly on OS X

[John Duncan]

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 because of the previous error.


So I tested this out in safe mode (with all add-ons) disabled, and the 
error seems to have disappeared. I will try going through each add-on to 
determine which one is causing this error.
- This has been an issue for awhile, but any time you click on an 
email or news message in mailnews, there is a type error in the 
'tabbrowser.xml' file


 Error: TypeError: browsers[i] is undefined
 Source File: chrome://navigator/content/tabbrowser.xml

The given line is: ``if (browsers[i].contentDocument == aDocument)"
(line 350)


followup error from the above.
But I thought this error has persisted at least since 2.40, and the 
errors above were only introduced in 2.50+




Sorry you are right. Do you use SeaTab X 2? I think its linked to it but 
not sure.
No, I do not. This error (browsers[i] is undefined] still persists even 
when I reboot into safe mode with all add-ons disabled, so I'm thinking 
it's perhaps unrelated to extensions? Once again, I could be wrong..


Yep, using the latest 2.50a1 tinderbox build (Dec. 25, build 
1482627108), all errors in the browser portion seem to be fixed. The 
workaround for installing addons seems to be working as well. It's 
styled a bit differently than on older versions, but seems to be 
functional.


http://i.imgur.com/5NlCHGt.png
http://i.imgur.com/VmA47K8.png

Yes the notifications changed. The needed CSS changes to 'deflat' it and 
make it more SeaMonkey friendly are not yet in.


Great. No worries; this is probably one of the nicest builds of SM I've 
ever used!


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

Re: SM 2.46 vs 2.50a1 nightly on OS X

[John Duncan]

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 one if the XUL and XPI deprecation goes thru as planned.


Thanks, I will give it a try. Hopefully, they don't actually go through 
with the XUL/XPCOM removal, but alas, it doesn't really seem like much 
can be done at this point.

There are a couple issues with 2.50 thus far, but they seem negligible:
- When you load a web page in a new tab, there is a type error:

 Error: TypeError: aArguments is undefined.
 Source File: chrome://navigator/content/tabbrowser.xml


Already fixed.


The given line is: ``aArguments.unshift(aBrowser);"
(line 419)

- When you open Mailnews, there is a syntax error in the 
'messengerdnd.js' file


 Error: SyntaxError: expected expression, got ')'
 Source File: chrome://messenger/content/messengerdnd.js


Already fixed.

Great!


The given line is: ``else if (types.includes("text/x-moz-url")))"
(line 242)

- When you open Mailnews, there is a syntax error in the 
'tabmail.xml' file


 Error: TypeError: tabinfo is undefined
 Source File: chrome://messenger/content/tabmail.xml

The given line is: ``let browserFunc = tabInfo.mode.getBrowser ||
   tabInfo.mode.tabType.getBrowser;"
(line 779)


followup error from the above.
Is it? Seems unrelated to the aArguments error, but maybe I'm missing 
something.


- This has been an issue for awhile, but any time you click on an 
email or news message in mailnews, there is a type error in the 
'tabbrowser.xml' file


 Error: TypeError: browsers[i] is undefined
 Source File: chrome://navigator/content/tabbrowser.xml

The given line is: ``if (browsers[i].contentDocument == aDocument)"
(line 350)


followup error from the above.
But I thought this error has persisted at least since 2.40, and the 
errors above were only introduced in 2.50+


- Installing add-ons from a .xpi file seems broken (updating from 
inside of about:addons or installing manually from a file still seems 
to work; it's just broken when you click on a .xpi file inside of the 
browser and the urlbar popup menu comes up broken)


 Here is a picture of what I am referring to: 
http://i.imgur.com/pjZn9fp.png



Not 100% fixed right now but a workaround is in. Works in current builds.


Cool.
- 2.46 had a regression wherein, when you viewed a large/tall image 
unscaled (by opening it in its own tab and clicking on it), portions 
of the top of it would become cut off as you scrolled up (it never 
lets you reach the top of the image). This is the same in 2.50.


 I tested this bug with this image: http://i.imgur.com/c1NOLaN.png


Probably a Gecko rendering bug. You should report it against Core. 
Maybe Layout Images. If not right someone will move it to the correct 
component.
Sounds good. Forgive me, as I looked around for the bug reports for 
those above (that have been fixed), but could not find the reports. 
Thanks for the info.


FRG


Yep, using the latest 2.50a1 tinderbox build (Dec. 25, build 
1482627108), all errors in the browser portion seem to be fixed. The 
workaround for installing addons seems to be working as well. It's 
styled a bit differently than on older versions, but seems to be functional.


http://i.imgur.com/5NlCHGt.png
http://i.imgur.com/VmA47K8.png


The mailnews errors are still there, as mentioned above. The 'tabinfo is 
undefined error' still happens when you first open the mailnews window, 
and the 'browsers[i] is undefined error' still happens when you click on 
any email or newsgroup message.


Everything else seems ultra fast and responsive. Great work!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM 2.46 vs 2.50a1 nightly on OS X

[John Duncan]

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 XPI deprecation goes thru as planned.


Thanks, I will give it a try. Hopefully, they don't actually go through 
with the XUL/XPCOM removal, but alas, it doesn't really seem like much 
can be done at this point.

There are a couple issues with 2.50 thus far, but they seem negligible:
- When you load a web page in a new tab, there is a type error:

 Error: TypeError: aArguments is undefined.
 Source File: chrome://navigator/content/tabbrowser.xml


Already fixed.


The given line is: ``aArguments.unshift(aBrowser);"
(line 419)

- When you open Mailnews, there is a syntax error in the 
'messengerdnd.js' file


 Error: SyntaxError: expected expression, got ')'
 Source File: chrome://messenger/content/messengerdnd.js


Already fixed.

Great!


The given line is: ``else if (types.includes("text/x-moz-url")))"
(line 242)

- When you open Mailnews, there is a syntax error in the 'tabmail.xml' 
file


 Error: TypeError: tabinfo is undefined
 Source File: chrome://messenger/content/tabmail.xml

The given line is: ``let browserFunc = tabInfo.mode.getBrowser ||
   tabInfo.mode.tabType.getBrowser;"
(line 779)


followup error from the above.
Is it? Seems unrelated to the aArguments error, but maybe I'm missing 
something.


- This has been an issue for awhile, but any time you click on an 
email or news message in mailnews, there is a type error in the 
'tabbrowser.xml' file


 Error: TypeError: browsers[i] is undefined
 Source File: chrome://navigator/content/tabbrowser.xml

The given line is: ``if (browsers[i].contentDocument == aDocument)"
(line 350)


followup error from the above.
But I thought this error has persisted at least since 2.40, and the 
errors above were only introduced in 2.50+


- Installing add-ons from a .xpi file seems broken (updating from 
inside of about:addons or installing manually from a file still seems 
to work; it's just broken when you click on a .xpi file inside of the 
browser and the urlbar popup menu comes up broken)


 Here is a picture of what I am referring to: 
http://i.imgur.com/pjZn9fp.png



Not 100% fixed right now but a workaround is in. Works in current builds.


Cool.
- 2.46 had a regression wherein, when you viewed a large/tall image 
unscaled (by opening it in its own tab and clicking on it), portions 
of the top of it would become cut off as you scrolled up (it never 
lets you reach the top of the image). This is the same in 2.50.


 I tested this bug with this image: http://i.imgur.com/c1NOLaN.png


Probably a Gecko rendering bug. You should report it against Core. Maybe 
Layout Images. If not right someone will move it to the correct component.
Sounds good. Forgive me, as I looked around for the bug reports for 
those above (that have been fixed), but could not find the reports. 
Thanks for the info.


FRG


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

Re: SM 2.46 vs 2.50a1 nightly on OS X

[John Duncan]

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. Deleting 
places.sqlite fixed the problem (I have a thousands of bookmarks and 
relatively extensive browser history), but I did not want to delete my 
places.sqlite file as I value my bookmarks and browsing history
Yes, I vacuumed the file to make sure it was not bloated. This does not 
happen with 2.50, so I will stay on this for awhile.


There are a couple issues with 2.50 thus far, but they seem negligible:
- no lightning builds will run on it (yet),
- When you load a web page in a new tab, there is a type error:

 Error: TypeError: aArguments is undefined.
 Source File: chrome://navigator/content/tabbrowser.xml

The given line is: ``aArguments.unshift(aBrowser);"
(line 419)

- When you open Mailnews, there is a syntax error in the 
'messengerdnd.js' file


 Error: SyntaxError: expected expression, got ')'
 Source File: chrome://messenger/content/messengerdnd.js

The given line is: ``else if (types.includes("text/x-moz-url")))"
(line 242)

- When you open Mailnews, there is a syntax error in the 'tabmail.xml' file

 Error: TypeError: tabinfo is undefined
 Source File: chrome://messenger/content/tabmail.xml

The given line is: ``let browserFunc = tabInfo.mode.getBrowser ||
   tabInfo.mode.tabType.getBrowser;"
(line 779)

- This has been an issue for awhile, but any time you click on an email 
or news message in mailnews, there is a type error in the 
'tabbrowser.xml' file


 Error: TypeError: browsers[i] is undefined
 Source File: chrome://navigator/content/tabbrowser.xml

The given line is: ``if (browsers[i].contentDocument == aDocument)"
(line 350)

- Installing add-ons from a .xpi file seems broken (updating from inside 
of about:addons or installing manually from a file still seems to work; 
it's just broken when you click on a .xpi file inside of the browser and 
the urlbar popup menu comes up broken)


 Here is a picture of what I am referring to: 
http://i.imgur.com/pjZn9fp.png



- XUL/XPCOM based extensions are still working well (I know Mozilla is 
planning on nixing these in the near future, as well all know), all 
plugins are working (including those that are not flash, such as 
Silverlight and Weppy [these did not work in 2.46, as all plugins other 
than flash are disabled]), the overall feel of the browser feels 
snappier (from what I can tell), and complete themes are working as 
well. For some reason my theme is not working in the Error Console, but 
the default theme does, so it must be something structural change that 
I'll need to update (this did not happen in 2.46).


- html5test scores are looking good in comparison to 2.46, as well.
With experimental about:config flags enabled, SM 2.50 scores a 505 out 
of 555.


- 2.46 had a regression wherein, when you viewed a large/tall image 
unscaled (by opening it in its own tab and clicking on it), portions of 
the top of it would become cut off as you scrolled up (it never lets you 
reach the top of the image). This is the same in 2.50.


 I tested this bug with this image: http://i.imgur.com/c1NOLaN.png
Also, there seems to be a bug where the back and forward buttons will 
not update to let you go either back or forward (depending on the 
circumstances). To fix this, you need to change tabs and come back to 
the tab that is bugged out.

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

SM 2.46 vs 2.50a1 nightly on OS X

[John Duncan]

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 fixed the problem (I have a thousands of bookmarks and 
relatively extensive browser history), but I did not want to delete my 
places.sqlite file as I value my bookmarks and browsing history
Yes, I vacuumed the file to make sure it was not bloated. This does not 
happen with 2.50, so I will stay on this for awhile.


There are a couple issues with 2.50 thus far, but they seem negligible:
- no lightning builds will run on it (yet),
- When you load a web page in a new tab, there is a type error:

Error: TypeError: aArguments is undefined.
Source File: chrome://navigator/content/tabbrowser.xml

The given line is: ``aArguments.unshift(aBrowser);"
(line 419)

- When you open Mailnews, there is a syntax error in the 
'messengerdnd.js' file


Error: SyntaxError: expected expression, got ')'
Source File: chrome://messenger/content/messengerdnd.js

The given line is: ``else if (types.includes("text/x-moz-url")))"
(line 242)

- When you open Mailnews, there is a syntax error in the 'tabmail.xml' file

Error: TypeError: tabinfo is undefined
Source File: chrome://messenger/content/tabmail.xml

The given line is: ``let browserFunc = tabInfo.mode.getBrowser ||
  tabInfo.mode.tabType.getBrowser;"
(line 779)

- This has been an issue for awhile, but any time you click on an email 
or news message in mailnews, there is a type error in the 
'tabbrowser.xml' file


Error: TypeError: browsers[i] is undefined
Source File: chrome://navigator/content/tabbrowser.xml

The given line is: ``if (browsers[i].contentDocument == aDocument)"
(line 350)

- Installing add-ons from a .xpi file seems broken (updating from inside 
of about:addons or installing manually from a file still seems to work; 
it's just broken when you click on a .xpi file inside of the browser and 
the urlbar popup menu comes up broken)


Here is a picture of what I am referring to: 
http://i.imgur.com/pjZn9fp.png


- XUL/XPCOM based extensions are still working well (I know Mozilla is 
planning on nixing these in the near future, as well all know), all 
plugins are working (including those that are not flash, such as 
Silverlight and Weppy [these did not work in 2.46, as all plugins other 
than flash are disabled]), the overall feel of the browser feels 
snappier (from what I can tell), and complete themes are working as 
well. For some reason my theme is not working in the Error Console, but 
the default theme does, so it must be something structural change that 
I'll need to update (this did not happen in 2.46).


- html5test scores are looking good in comparison to 2.46, as well.
With experimental about:config flags enabled, SM 2.50 scores a 505 out 
of 555.


- 2.46 had a regression wherein, when you viewed a large/tall image 
unscaled (by opening it in its own tab and clicking on it), portions of 
the top of it would become cut off as you scrolled up (it never lets you 
reach the top of the image). This is the same in 2.50.


I tested this bug with this image: http://i.imgur.com/c1NOLaN.png
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM 2.46 Silverlight plugin/DRM support

[John Duncan]

John Duncan wrote:
Any news on whether or not SeaMonkey will support Google Widevine CDM at 
any point in the near future? It's a shame that I can no longer watch 
netflix in SeaMonkey 2.46.
I have decided to instead just use the nightly version of SM 2.50, which 
still allows plugins (other than flash and the built in apple default 
browser helper) to run.


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

SM 2.46 Silverlight plugin/DRM support

[John Duncan]

Any news on whether or not SeaMonkey will support Google Widevine CDM at 
any point in the near future? It's a shame that I can no longer watch 
netflix in SeaMonkey 2.46.

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

Re: Mnenhy with 2.46

[John Duncan]

Jonathan N. Little wrote:

Didn't someone post a fix for Mnenhy with 2.46? I thought I saw it but
cannot find the post. Had a bit of a panic because it messed up my
header panel which interfered with Enigmail decoding message in one of
my accounts...

>FWIW, mnenhy already displays Xface

>Take a look at the diff I posted, you'll see what was needed to fix
the extension. Apparently, there was a change in ES6 syntax?

>https://pastebin.mozilla.org/8930566
>https://www.sitepoint.com/preparing-ecmascript-6-let-const/
>https://en.wikipedia.org/wiki/ECMAScript#6th_Edition_-_ECMAScript_2015

^ this was Mason83's reply to my post in that chain. Probably what 
you're referring to.

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

Re: 2.46 version

[John Duncan]

Edmund Wong wrote:

Pat Connors wrote:

In the interim since the 2.40 breach was discovered, I have been using
2.47 64 bit with no problems what so ever.  Question, when 2.46 is
available for download, should I use it or stay with the 2.47 version?


Breach? What breach?

Edmund


I think he's referring to the SVG 0-day javascript exploit
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM2.46 default search engine problem

[John Duncan]

Frank-Rainer Grahl wrote:

Use the force (or google search).

Known bug. See https://bugzilla.mozilla.org/show_bug.cgi?id=1265881 for 
a workaround.


Or open Sidebar. Set search engine and do one search from there. Default 
engine should be set to this one then.


FRG


John Duncan wrote:

EE wrote:

cmcadams wrote:

I've just installed SM2.46, and discovered that the engine pick list in

Edit > Preferences > Browser > Internet Search

isn't working. I got my choice by deleting all the alternatives, which
becomes the new unchangeable option even if you then Restore Defaults.

Not a killer, because it can be gotten around, but still annoying.

User agent: Mozilla/5.0 (Windows NT 6.1; rv:49.0) Gecko/20100101
Firefox/49.0 SeaMonkey/2.46


My search bar is working.  I can change the search engine to whatever is
listed in there, and I put my own preferred engines in there.
I am using SM 2.46.  I use Mac OS, so is this problem just a Windows
problem?


I am getting the same problem on SM 2.46 in OS X 10.11.6.

I can set the default search engine in the preferences dialog, but 
that does not change the default search engine for the url bar; it is 
always 'DuckDuckGo'



Doh. Much appreciated! Forgot to check the bug report for workaround.

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

Re: SM2.46 default search engine problem

[John Duncan]

EE wrote:

cmcadams wrote:

I've just installed SM2.46, and discovered that the engine pick list in

Edit > Preferences > Browser > Internet Search

isn't working. I got my choice by deleting all the alternatives, which
becomes the new unchangeable option even if you then Restore Defaults.

Not a killer, because it can be gotten around, but still annoying.

User agent: Mozilla/5.0 (Windows NT 6.1; rv:49.0) Gecko/20100101
Firefox/49.0 SeaMonkey/2.46


My search bar is working.  I can change the search engine to whatever is
listed in there, and I put my own preferred engines in there.
I am using SM 2.46.  I use Mac OS, so is this problem just a Windows
problem?


I am getting the same problem on SM 2.46 in OS X 10.11.6.

I can set the default search engine in the preferences dialog, but that 
does not change the default search engine for the url bar; it is always 
'DuckDuckGo'

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

Re: SeaMonkey v2.46 Build number 8 blog...

[John Duncan]

Ant wrote:

On 12/13/2016 12:02 AM, Ant wrote:

https://blog.seamonkey-project.org/2016/12/13/build-number-7/


   https://blog.seamonkey-project.org/2016/12/13/build-8/

Sounds promising! Hang in there, guys; your work is highly appreciated.

What exactly is the problem with the Lightning/DOM Inspector/Chatzilla 
repacks, again? Is it something to do with locales not being correctly 
identified?

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

Re: akalla version 2.46 issues

[John Duncan]

Mason83 wrote:

On 22/11/2016 15:54, TCW wrote:


On Sun, 20 Nov 2016 21:08:09 +0100, Mason83 wrote:


On 20/11/2016 20:50, Mason83 wrote:

On 20/11/2016 20:47, Mason83 wrote:

On 20/11/2016 20:44, Mason83 wrote:


2) When I display an email or NG message, the header pane was empty.
Removing the Mnenhy add-on seems to have fixed that.
Will try reinstalling.


https://addons.mozilla.org/en-US/seamonkey/addon/mnenhy/

Breaks the header pane...

Incompatible with Lightning?


Disabling Lightning doesn't help :-(

Maybe Mnenhy is just not compatible with SM 2.46?

https://addons.mozilla.org/en-US/thunderbird/addon/mnenhy/
says Works with Thunderbird 3.0 - 29.0a1

If anyone is using that extension on SM 2.46 or higher,
I'm all ears.


Last Updated: February 25, 2014

Probably broken by the upgrade tread-mill :-(

I used it for Message-ID Search and Custom Headers/X-Faces.

Any other extension supporting those features?

Regards.


Probably just a dead and unsupported add-on.


It is likely that the original author has stopped working on that
add-on. However, someone else picked up the ball:

https://www.mozdev.org/bugs/show_bug.cgi?id=26256#c2
https://bitbucket.org/stanio/mnenhy/downloads

Here are the differences between
mnenhy-0.8.6-fx+tb+sm.zip (the original from amo)
and
mnenhy-0.8.6.1.2-stanio.zip (the update from stanio)

https://pastebin.mozilla.org/8930566

Same diff, ignoring white-space changes and lines starting
with "let", "var", or "const"

https://pastebin.mozilla.org/8930568

Ratty and frg said the changes are just syntactic.

Regards.

Would this breakage have anything to do with the fact that the XUL/XPCOM 
SDK is being deprecated in the near future? I am writing/maintaining a 
similar add-on (to display Face/X-Face/etc. headers in the header area), 
and I think that my add-on will most likely break soon too.


https://github.com/JohnDDuncanIII/MessageFaces
^ url, if you're interested.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Good news for adventurous MAC - SeaMonkey - users ...

[John Duncan]

EE wrote:

Rainer Bielefeld wrote:

... you can find here .

Best regards


Rainer


Exactly where is the Mac release?  I could not find it.  All I could
find was the notice about it.


https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-mac64/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Lightning Add-on no longer available for SeaMonkey?

[John Duncan]

NoOp wrote:

Is Lightning no longer available for SeaMonkey 2.40? Went to
update/install on a system and ran into "Not available for SeaMOnkey
2.40" see:


What's up with that?

Does every new SeaMonkey 2.40 user now need to go to:

and load 4.5b1 (Beta) directly now?


https://addons.mozilla.org/seamonkey/downloads/file/383795/lightning-4.5b1-sm+tb-mac.xpi

https://addons.mozilla.org/en-us/seamonkey/addon/lightning/versions/beta

you need to manually go to the beta versions on AMO, I think.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey and Netflix

[John Duncan]

JAS wrote:

Running SM 2.40 on Win 7 machine. Latest Silverlight and Adblock Plus is
disabled. User Agentis set in about:config with --
general.useragent.override.netflix.com;Mozilla/5.0 (Windows NT 6.1;
WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 Can not connect to watch
Netflix and just get a black screen, any ideas ?? works alright on my XP
machine.

JAS
Verified works-for-me on OS X 10.11.5 using latest silverlight and 
ublock origin. my about:config override is:
general.useragent.override.netflix.com;Mozilla/5.0 (Macintosh; Intel Mac 
OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0

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

Re: Newsgroup Disconnect

[John Duncan]

David E. Ross wrote:

On 4/8/2016 9:37 PM, OG wrote:

I use two providers to look at the same newsgroups.
I boot the laptop and Seamonkey updates the newsgroups.

I let the app sit all day open so that I can get the latest updates when
I return.

But seamonkey refuses to look at either provider giving an error message
that it cannot access the provider at any of the newsgroups.

But FireFox can go to the internet and load a fresh page e.g. google news.

Restarting seamonkey does not fix the problem.

I am connected to my home network via wifi and it is a good strong
signal and speedtest.net indicates full speed.

If I reboot the laptop I get access to the newsgroups.

What is going on?

Is there something I need to do in Seamonkey to get it talking to the
newsgroups?

If I Compose an new post then Seamonkey again has access to the listed
newsgroups.  What is this all about?



On what newsgroup server do you see this?  Do you see this with
news.mozilla.org?

I'd just like to chime in to say that this happens to me on occasion 
(using SM 2.39 and 2.40 on OS X). Not really sure how it fixes itself 
(as I only check USENET newsgroups a few times a day), but it has never 
been annoying enough for me to really notice.

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

Re: Macintosh El Capitan compatible?

[John Duncan]

Gini Moore wrote:

Just wondering if Sea Monkey works on El Capitan? Donʻt want to upgrade if it 
doesnʻt.


Yes, it works fine. Using 2.40 on 10.11.3 right now.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.40?

[John Duncan]

Paul Bergsagel wrote:

Cruz, Jaime wrote:

It's been awhile, and Firefox has already had multiple releases since
Seamonkey 2.39.  What's the story?


I believe SeaMonkey 2.40 is presently in the works. The programmer in
charge of compiling the code broke his arm (I think?), so there is a
delay in producing the new version.

Anyway I am happy to wait to get the next SeaMonkey version. Thanks to
all the programmers who help to produce my favourite browser/email
program. Your work is very much appreciated.

from https://blog.mozilla.org/meeting-notes/archives/2335 :

SeaMonkey 2.40 final (tracking bug 1233615) is in progress: in limbo.

Without ewong we are stuck.
IanN to check with Callek_cloud9 to see if he can help.
build #4 are up for all platforms and locales
Windows builds aren’t signed yet
apparently there is an issue with uploading those builds to the new 
S3 infrastructure [1] See bug 1223633 and bug 1213721


comm-release default tip is on 2.41 now.


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

Re: New problems printing draft emails

[John Duncan]

Bill Spikowski wrote:

Bill Spikowski wrote:

I recently upgraded SM from 2.26 to 2.39 and have noticed a new
problem (across several computers and OS's).

When I'm composing an email, I often print a draft -- because I can
proofread better on paper than on the screen.

I no longer can print using FILE | PRINT or using the Print button on
the toolbar

But I use the print preview feature, I can print from there.

Anyone have an idea what might cause this behavior?


I see through Google that others have reported this behavior in recent
versions of Seamonkey -- basically, in the compose window, the 'print'
function no longer works, unless the user invokes it from the 'print
preview' window.

Maybe I'm one of the few people who print drafts of my email from the
compose window -- I've done this dozen of times each day for more years
than I can remember

Now I hit 'print' and go about my business, wondering later why nothing
printed -- unless I remember the problem and go to 'print preview' first.

I'm still trying to find a workaround that doesn't require me to unlearn
deep-seated behavior! For instance I've been looking for a dedicated
'print' button for the toolbar in the compose window. The one I have
performs the same as FILE | PRINT -- is there a way I could manipulate
whatever's behind this button so it invokes 'print preview' instead?



Same thing here on OS X using SM 2.39. File -> Print and command+p does 
nothing.

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

Re: Download Video?

[John Duncan]

»Q« wrote:

In ,
"David E. Ross"  wrote:


My daughter posted videos of my granddaughter on YouTube.  How can I
download these to save with photos of my granddaughter?


 will do
it, but you may not get the highest quality.  I prefer the command
line youtube-dl, , which by default
will get the highest quality, combining the best audio and best video
if necessary.  I haven't tried it on Windows, though.



+1 for the youtube-dl program. Works fine on Windows (in fact, they 
provide a binary[0] youtube-dl.exe on their website). Best used in 
conjunction with the mpv[1] media player.


[0]: https://rg3.github.io/youtube-dl/download.html
[1]: https://mpv.srsfckn.biz/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Cookie or sniffing issue:?

[John Duncan]

Paul B. Gallagher wrote:

I'm trying to renew my vehicle registration with the Pennsylvania
Department of Motor Vehicles (PennDOT), but the site seems to be broken
in a way I can't figure out (I've done this for 10 years running and
it's never been a problem until now). And the gist of PennDOT's response
is, "it works on my machine, so it must be your fault and I refuse to
help."

I begin here: , which immediately redirects to
. In the menu on
the left, I click "Renew Your Vehicle Registration," which ostensibly
points to
,
but instead redirects me to an error page at
:

"We Cannot Process Your Request. The service you have selected uses
non-persistent cookies. Your browser is not currently set up to allow
non-persistent cookies."

Now, my default cookie policy is to accept only first-party session
cookies, but apparently they want me to accept third-party cookies
without time restriction. So I clear cache and cookies, set the prefs at
Edit | Preferences | Privacy & Security | Cookies to
(•) Allow all cookies
(•) Accept cookies normally
and restart the browser. When I return, nothing has changed -- PennDOT
still says I'm not set up to accept their cookies. I check the Cookie
Manager, and I have two cookies from pa.gov and four from www.pa.dmv.gov
but none from any third-party site.

So my questions are:

1) Has the webmaster miscoded his cookie-setting/reading routine,
causing it to fail? This doesn't happen with Internet Exploiter 11.

2) Could the webmaster be using a bad sniffer that rejects SM out of hand?

3) Is there an issue with SeaMonkey's processing of cookies, such that
it doesn't handle some cookies even though it says it will?

Thanks.

It seems as if it could be any of those issues. The strange part is, I 
just tried this, and was not lead to any error page whatsoever. Seems to 
work on my machine. Have you tried using a clean/test profile?

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

Re: 2.39 and system hanging

[John Duncan]

John Duncan wrote:

Edmund Wong wrote:

Hi,

Is it just me, or does 2.39 hang a lot?  Especially with
getting email?   After clicking get messages, it'd download
the stuff, and then hang for about ten seconds or so and
then resume (after switching windows on me).  Like say
I am in the 3-pane message window.  I click on "Get Msgs".
It'd download the mail.  Then hang.  Once it resumes,
it jumps to some other browser window.

Mind you, this is with an old profile.  Guess I'll try
it with a new one.

Ed


I have not experienced this. I have experienced strange bugs in OS X
(since as far back as 2.33.1 and before) where when I open an e-mail for
the first time after starting the suite, my CPU will get maxed out and
the browser will freeze up for about 30 seconds while the system process
for getting contact data does its thing. This also happens when I open
the browser file manager thing for OS X when I save an image or piece of
media from the web (for the first time after starting it - afterwords
it's fine).

Similar bugs I've encountered on my machine recently (I have not
confirmed any or send any to bugzilla, as I have not tested them on a
clean profile):

Other ones I can think of off the top of my head - the searchbar for the
bookmarks window (command+b / ctrl+b) is no longer visible in 2.39. It
is still visible in the XUL
(chrome://communicator/content/bookmarks/bm-panel.xul)
(chrome://communicator/content/bookmarks/bookmarksManager.xul) and
sidebar, so I'm assuming this is a regression specific to that window
type or something. Also seems as if the close button in the sidebar no
longer highlights when dragging the mouse over it (this could be a
problem with my theme though).

about:support does not display with the color of the system highlight
color on OS X anymore (this has been broken since around 2.33.1 or so I
believe).

the current version of the lightning calendar add-on is broken in terms
of the toolbar icons (none show - I remember this happening to the
nightly version around August of this year). Release version affected is
4.4b2 for SM 2.39 release.

Also I'm not sure if this is just me or not, but the default SeaMonkey
theme does not seem to have any grippies for quickly collapsing
toolbars, and I have found no discernible way to show the Bookmarks
Toolbar or Website Navigation Bar with the default theme activated in a
browser window. (not sure how long this has affected my install - could
be one of the changes in my userChrome.css that I could troubleshoot,
but I don't think it is..)

I'm also not sure what has caused this, but I remember when I was using
2.39 nightly (I think?) running https://html5test.com/ would return a
score of 509, and it now returns 501 on my machine. "Speech
Recognition," and "Pointer Events" both used to register as "Yes" but
are no longer found on the 2.39 release version.
Also, netflix does not work for me in SeaMonkey 2.39 with the most 
recent version of silverlight. works fine in safari and in the most 
recent webkit nightly.

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

Re: 2.39 and system hanging

[John Duncan]

Edmund Wong wrote:

Hi,

Is it just me, or does 2.39 hang a lot?  Especially with
getting email?   After clicking get messages, it'd download
the stuff, and then hang for about ten seconds or so and
then resume (after switching windows on me).  Like say
I am in the 3-pane message window.  I click on "Get Msgs".
It'd download the mail.  Then hang.  Once it resumes,
it jumps to some other browser window.

Mind you, this is with an old profile.  Guess I'll try
it with a new one.

Ed

I have not experienced this. I have experienced strange bugs in OS X 
(since as far back as 2.33.1 and before) where when I open an e-mail for 
the first time after starting the suite, my CPU will get maxed out and 
the browser will freeze up for about 30 seconds while the system process 
for getting contact data does its thing. This also happens when I open 
the browser file manager thing for OS X when I save an image or piece of 
media from the web (for the first time after starting it - afterwords 
it's fine).


Similar bugs I've encountered on my machine recently (I have not 
confirmed any or send any to bugzilla, as I have not tested them on a 
clean profile):


Other ones I can think of off the top of my head - the searchbar for the 
bookmarks window (command+b / ctrl+b) is no longer visible in 2.39. It 
is still visible in the XUL 
(chrome://communicator/content/bookmarks/bm-panel.xul) 
(chrome://communicator/content/bookmarks/bookmarksManager.xul) and 
sidebar, so I'm assuming this is a regression specific to that window 
type or something. Also seems as if the close button in the sidebar no 
longer highlights when dragging the mouse over it (this could be a 
problem with my theme though).


about:support does not display with the color of the system highlight 
color on OS X anymore (this has been broken since around 2.33.1 or so I 
believe).


the current version of the lightning calendar add-on is broken in terms 
of the toolbar icons (none show - I remember this happening to the 
nightly version around August of this year). Release version affected is 
4.4b2 for SM 2.39 release.


Also I'm not sure if this is just me or not, but the default SeaMonkey 
theme does not seem to have any grippies for quickly collapsing 
toolbars, and I have found no discernible way to show the Bookmarks 
Toolbar or Website Navigation Bar with the default theme activated in a 
browser window. (not sure how long this has affected my install - could 
be one of the changes in my userChrome.css that I could troubleshoot, 
but I don't think it is..)


I'm also not sure what has caused this, but I remember when I was using 
2.39 nightly (I think?) running https://html5test.com/ would return a 
score of 509, and it now returns 501 on my machine. "Speech 
Recognition," and "Pointer Events" both used to register as "Yes" but 
are no longer found on the 2.39 release version.

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

Re: Netflix SM 2.39

[John Duncan]

BL wrote:

Since SeaMonkey update to 2.39 I have problem with Netflix. Movie
selection loads normally but playback stays at black screen and no
sound. I reinstalled Silverlight but problem remains. Netflix plays
normally on FF and IE.Any ideas??
Thank You  BL
Same here! Using Silverlight 5.1.40728.0 on OS X 10.11.2 - I get a black 
screen. Seems as if that is one of the few regressions that have 
happened on 2.39.


Other ones I can think of off the top of my head - the searchbar for the 
bookmarks window (command+b / ctrl+b) is no longer visible. It is still 
visible in the XUL 
(chrome://communicator/content/bookmarks/bm-panel.xul) 
(chrome://communicator/content/bookmarks/bookmarksManager.xul) and 
sidebar, so I'm assuming this is a regression specific to that window 
type or something. Also seems as if the close button in the sidebar no 
longer highlights when dragging the mouse over it (this could be a 
problem with my theme though).


about:support does display with the color of the system highlight color 
on OS X anymore (this has been broken since around 2.33.1 or so I believe).


the current version of the lightning calendar add-on is broken in terms 
of the toolbar icons (none show - I remember this happening to the 
nightly version around August of this year). Release version affected is 
4.4b2 for SM 2.39 release.


Also I'm not sure if this is just me or not, but the default SeaMonkey 
theme does not seem to have any grippies for quickly collapsing 
toolbars, and I have found no discernible way to show the Bookmarks 
Toolbar or Website Navigation Bar with the default theme activated in a 
browser window. (not sure how long this has affected my install - could 
be one of the changes in my userChrome.css that I could troubleshoot, 
but I don't think it is..)


I'm also not sure what has caused this, but I remember when I was using 
2.39 nightly (I think?) running https://html5test.com/ would return a 
score of 509, and it now returns 501 on my machine. "Speech 
Recognition," and "Pointer Events" both used to register as "Yes" but 
are no longer found on the 2.39 release version.

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

Re: SeaMonkey 2.39b1 released

[John Duncan]

Edmund Wong wrote:

Greetings,

The SeaMonkey Project is pleased to announce the release of SeaMonkey
2.39b1!

For a more complete list of changes in SeaMonkey 2.39b1, see the What's
New in SeaMonkey 2.39b1 section of the Release Notes [2], which also
contain a list of known issues and answers to frequently asked
questions. For a more general overview of the SeaMonkey project (and
screen shots!), visit www.seamonkey-project.org.

Links:
[1] - http://www.seamonkey-project.org/releases/2.39b1
[2] - http://www.seamonkey-project.org/releases/seamonkey2.39/

So soon! Great work guys. Not sure if it's a bug in my current theme or 
not, but the search bar in 2.39b1 does not show up in the command+b 
Bookmarks window. Still there in 
chrome://communicator/content/bookmarks/bm-panel.xul though. I'll test 
that in safe mode later tonight..

http://i.imgur.com/NyE47BW.png
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMoneky 2.38 is out of date

[John Duncan]

Ray_Net wrote:

John Duncan wrote on 19/10/2015 05:33:

Marisa Ciceran wrote:

Others have probably already reported this, so please forgive me if I am
being repetitive. Once again, JPMorgan Chase Bank (http://chase.com)
does not recognize Seamonkey version  2.38. When I go to their Home
page, it states:

Please upgrade your browser.

Your browser is out of date. For a faster and more secure online
experience upgrade your browser to the most recent version. Click
here for a list of recommended browsers
<https://www.chase.com/services/browser-update.html>.

Unlike prior occasions when this had happened, this time it lets me log
in anyway, but each times their system goes through a process of
verifying my PC as if it is "new" to their system. Any suggestions on
how to get rid of this nagging process?

Thanks,

Marisa


Other than setting a custom user agent to /only/ advertise the firefox
version (simply remove the `SeaMonkey/2.38' so it ends with
`Firefox/41.0.'), I'm not sure what you'd do.

This is an annoying process, as you would have to manually update it
each time you update your version of SeaMonkey, but it would probably
work. if you go to your about:config, and add a New -> String with
name: "general.useragent.override" and value: "[your old user-agent
minus the semaonkey portion]"
for me, this would be: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11;
rv:41.0) Gecko/20100101 Firefox/41.0"

I simply removed the `SeaMonkey/2.38' and `Lightning/4.3b2' portions
from my normal user agent (you can use something like
http://whatsmyuseragent.com/ if you're not sure what your exact UA
is). This could possibly fix your issue, if that's indeed your they're
doing their browser sniffing. Perhaps that's happening because it
can't save the cookie correctly?

- John D.


So SeaMonkey will never been recognized by webmasters  It' better to
contact the bank 

Anyway, you can close this pop-up ignoring their stupid alert :-)
I looked to see if there was anyway of contacting the bank by email - I 
could not find anything!

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

Re: SeaMoneky 2.38 is out of date

[John Duncan]

Marisa Ciceran wrote:

Others have probably already reported this, so please forgive me if I am
being repetitive. Once again, JPMorgan Chase Bank (http://chase.com)
does not recognize Seamonkey version  2.38. When I go to their Home
page, it states:

Please upgrade your browser.

Your browser is out of date. For a faster and more secure online
experience upgrade your browser to the most recent version. Click
here for a list of recommended browsers
.

Unlike prior occasions when this had happened, this time it lets me log
in anyway, but each times their system goes through a process of
verifying my PC as if it is "new" to their system. Any suggestions on
how to get rid of this nagging process?

Thanks,

Marisa

Other than setting a custom user agent to /only/ advertise the firefox 
version (simply remove the `SeaMonkey/2.38' so it ends with 
`Firefox/41.0.'), I'm not sure what you'd do.


This is an annoying process, as you would have to manually update it 
each time you update your version of SeaMonkey, but it would probably 
work. if you go to your about:config, and add a New -> String with name: 
"general.useragent.override" and value: "[your old user-agent minus the 
semaonkey portion]"
for me, this would be: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; 
rv:41.0) Gecko/20100101 Firefox/41.0"


I simply removed the `SeaMonkey/2.38' and `Lightning/4.3b2' portions 
from my normal user agent (you can use something like 
http://whatsmyuseragent.com/ if you're not sure what your exact UA is). 
This could possibly fix your issue, if that's indeed your they're doing 
their browser sniffing. Perhaps that's happening because it can't save 
the cookie correctly?


- John D.

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

Re: Is 360 degrees YouTube videos supposed to work in SeaMonkey?

[John Duncan]

David E. Ross wrote:

On 10/8/2015 9:06 AM, Ant wrote:

Example: https://www.youtube.com/watch?v=7WERjL-mpPQ even with HTML5
working. It didn't work in both of my Linux/Debian oldstable and Windows
XP Pro SP3 boxes. It works in Chrome though!

Thank you in advance. :)



YouTube apparently sniffs the user agent (UA) for Firefox.  With the
following UA -- set via my own tailoring of PrefBar -- I was able to
view the video:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101
SeaMonkey/2.38, NOT Firefox/41.0


Works on my machine using the default SeaMonkey 2.38 UA on OS X:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:41.0) Gecko/20100101 
Firefox/41.0 SeaMonkey/2.38 Lightning/4.3b2

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

Re: Color Preferences

[John Duncan]

David E. Ross wrote:

What do the different settings of the preference variable
browser.display.document_color_use mean?  This variable is not
documented at .

Cross-posted to mozilla.dev.apps.seamonkey and mozilla.support.seamonkey
Followup-To:  mozilla.support.seamonkey

Seems like it has something to do with overriding page colors? Phil 
might know the specifics..


https://github.com/mozilla/releases-comm-central/blob/master/mail/components/preferences/colors.xul

https://groups.google.com/forum/#!topic/mozilla.dev.platform/th7gTtRSgo0

Snippet from the related XUL:

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

Re: Good news coming for users of Adblock Plus

[John Duncan]

Mason83 wrote:

On 26/09/2015 13:43, Ant wrote:


On 9/25/2015 1:27 PM, Mason83 wrote:


http://venturebeat.com/2015/09/23/mozilla-fixed-a-14-year-old-bug-in-firefox-and-now-adblock-plus-uses-a-lot-less-memory/
https://bugzilla.mozilla.org/show_bug.cgi?id=77999

https://blog.mozilla.org/nnethercote/2015/07/01/firefox-41-will-use-less-memory-when-running-adblock-plus/
https://blog.mozilla.org/nnethercote/2014/05/14/adblock-pluss-effect-on-firefoxs-memory-usage/


So we will see this in the upcoming SM v2.38?


Yamo said SM 2.38 will be based on Gecko 41.
So I think the answer is yes.

I use ABP, and the SM process often consumes 1.5-2.0 GB
(I have 20-30 tabs open.)

Regards.

2.38 seems very good on memory usage so far on my end (OS X 10.11). I 
use µBlock origin, so the fix does not affect me, but I've been writing 
a paper today with around 20-30 tabs open (including google docs, long 
wiki-like pages, youtube videos, etc.) and I only just reached 1GB 
memory usage, which is really nice (I also run /a lot/ of various 
addons). I have noticed some regressions when it comes to the html5test, 
but the regressions seem to be on their end as features like MediaSource 
extensions and the like all seem to be working, despite the feedback 
that the site is giving.

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

Re: SeaMonkey 2.38 released

[John Duncan]

Philipp van Hüllen wrote:

Edmund Wong wrote:

The SeaMonkey Project is pleased to announce the release of SeaMonkey
2.38!


When running SM 2.38b1 - is there any reason to switch to 2.38?

(I think to remember, that earlier on the last beta was practically
equal to the release version - not 100% sure, though.)

/Philipp
I had a few strange issue in 2.38b1 that were fixed in 2.38. I'd 
recommend upgrading.

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

Re: SeaMonkey 2.35..

[John Duncan]

Edmund Wong wrote:

Hi,

I regret to be the bearer of bad news; but as it stands,
the worst case scenario (and likely the actual case) is that 2.35 is
not going to be released in July.

The new goal is to release it in early August.

The past month has been mired in fire-fighting bustages,
getting repacks and builds working (as of this writing,
trunk is busted) as well as the need to get the backend
buildbot code updated to reflect that we no longer depend
on CVS.

I apologize for the delay and thank everyone for your
patience.

Edmund

thanks for the update, Ed! These things happen. The future still looks 
bright though.


If anyone else is interested, I tried out the latest OS X trunk builds 
that have been built in the past few days and they are (at least on my 
profile), busted to the point where after an hour or so of use, no 
webpages load, the browser uses 100% of the CPU, and the only way to 
exit is to force close. When you re-open the browser, it will continue 
to not load any webpages and utilize 100% of the cpu until a force quit 
is required. I'd recommend for OS X users that like to be as up to date 
as possible to stay on Build identifier: 20150706003002 
(http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2015-07-06-00-30-02-comm-central-trunk/seamonkey-2.39a1.en-US.mac.dmg). 
This build was the last stable-unstable build that I have come across 
recently. The latest lightning nightly works very well for this build as 
well.

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

Re: Add Mail Account

[John Duncan]

David Guymer wrote:

Is there a way to add a mail account with the corrupted mail/news wizard
that is a known fault for SeaMonkey 2.33.1

Windows 7 Home Premium (Soon to be Windows 10)

TIA
David G
Yes, go to your about:config page and search for 
`mail.identity.idX.valid' and see if any of them are false. If so, right 
click and reset them or set them to true. This will fix the account 
creation wizard for now. This is a known bug 680003 
[https://bugzilla.mozilla.org/show_bug.cgi?id=680003]

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

Re: Flash plug-in

[John Duncan]

rjkrjk wrote:

follow the link to adobe, and d/l current version 1800 209



Paul in Houston, TX wrote on 7/14/2015 12:27 AM:

Paul Bergsagel wrote:

I got the message in SeaMonkey "Shockwave Flash is venerable. Use
with caution" yesterday
and updated to the latest up to date flash plug-in.

Today I get the same warning about flash. I clicked on the add-ons
manager under the Tools
menu and clicked on "Check to see if your plugins are up to date"
which takes me to
https://www.mozilla.org/en-US/plugincheck/  only to inform me that
all versions of Adobe's
Flash Player are currently vulnerable.

BTW I am using MacOS X. How safe is it to activate flash when it has
been blocked by
Seamonkey because it is outdated?

Thanks,
Paul.


https://helpx.adobe.com/security/products/flash-player/apsa15-04.html

How safe?  That's relative to YOUR browsing habits and computer
knowledge.
I am not the least bit concerned about my machines.
The small kids next door probably already have their computers infected.

A good point, but still, technically speaking, all versions of flash 
(and newer versions of the java plugin) have some nasty new 0-days 
because of that stupid italian ``hacking team'' that recently themselves 
got hacked. Still, with good browsing habits and a bit of common sense, 
most power users should be fine.

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

Re: SeaMonkey Update Fails Because A 2nd Copy Is Running ???

[John Duncan]

Rick Merrill wrote:

HenriK wrote on 07/12/2015 4:58 PM:

Paul B. Gallagher wrote:

HenriK wrote:

Paul B. Gallagher wrote:

HenriK wrote:


In trying to update a copy of SM v.2.30 to the latest version on a
Win7Home Premium PC, the update fails and an error message is
returned claiming a 2nd version of SM is running.  After a
file-by-file search using Windows Explorer, I couldn't find any
evidence of a 2nd copy of SM but I wasn't clear about what evidence I
should have been looking for.


Try looking at the "Processes" tab of Windows Task Manager
(CTRL-SHIFT-ESC). Do you see any SeaMonkeys there?

This sometimes occurs when SM doesn't shut down correctly.


Thanks for the thought.  I looked in Task Manager and didn't see
anything beyond the single copy I thought I was running.

I wonder if the problem could be caused by some stray bit of material
lurking in the registry?

If I tell Control Panel to deinstall SeaMonkey, my understanding is
that
the profile, mail, bookmarks, etc., do NOT get deleted.  Is that a
correct understanding?  If so, might a SM deinstallation and
installation of the most recent SM version solve my problem? Or, would
a deinstallation/new installation create more trouble?


Precisely that advice has been given many times in this forum by
authoritative experts, just as you say.

Worth a try, once you've shut down all copies/versions of SM. If you
still get the error message even when WTM says you're clear, post back.


I am really confused. Win7 Home Task Manager consistently indicates no
SM is running after a deinstall of v.2.30. Fortunately, my profile
info was left untouched by the v.2.30 deinstall process.  BUT, I still
get the error message that the v.2.33.1, the newest version won't
install because another copy of SM (version not stated) is running.
After clicking past the error message window, however, I find that
v.2.33.1 has, in fact, been installed.  How do I get rid of this
nuisance error message?

Although I have been around since the MS-DOS days and don't really
understand much about any Windows version after W98, I can't help but
wonder if some odd bid of something has been left by the SM v.2.30
deinstall process in the registry or some other obscure place or that
the v.2.33.1 install mechanism code fails to do something it was
supposed to do.  Again, any ideas on how to get rid of the nuisance
error message and what is causing this problem?

Thanks, in advance for pointers to tutorials, and any suggestions or
advice.

Knowing nothing about the issue, I am reminded of times when I had to
reboot the whole computer because some program had left an in-use flag
on a file that a program needed and only a reboot would clear it.
That's why I always loved that program ``Unlocker 1.9.2,'' before it was 
bundled with spyware :/


Fixed that issue beautifully.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: How dead is SeaMonkey?

[John Duncan]

Danny Kile wrote:

Mason83 wrote:

On 08/07/2015 05:05, Paul Bergsagel wrote:


Maybe the time has come to reconsider how often SeaMonkey needs to be
updated. Does SeaMonkey benefit, in the long run, with such a rapid
update schedule?  If SeaMonkey adopted a less frequent update schedule
would the net benefits be greater than if SeaMonkey continued with the
current rapid update schedule?


Funny you should say that!

https://mail.mozilla.org/pipermail/firefox-dev/2015-July/003063.html
http://venturebeat.com/2015/07/06/mozillas-plans-for-firefox-more-partnerships-better-add-ons-faster-updates-and-more/




So with Firefox going to a more aggressive releases dates will SeaMonkey
be able to keep up? I was hoping for a less aggressive release process.
Oh well it is what what it is we will have to wait and see.

Danny
I'm assuming it's going to stay relatively similar to how it is right 
now. Firefox ``releases'' will increase in speed, but the SeaMonkey 
community will probably just merge big security updates from ESR and 
leave all of the extra crap out, as usual. I don't really see any change 
coming in the near future to this system to be honest. Bug fixes should 
be the biggest priority for this community in the immediate future.

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

Re: How dead is SeaMonkey?

[John Duncan]

Edmund Wong wrote:

Ed Mullen wrote:

I've seen several sort of oblique mentions here of the lack of
development of SM.  Also, haven't seen an update in a while.  So, I'm
beginning to feel that I'm nearing the point where I cannot any longer
stick with SM.

Kind of sad since I've been with it since Netscape back in, about, 1995.
  I don't have any aversion to "an end of an era" but it would be nice
to get some definitive info on what the few remaining SM devs are doing
or have in mind.

Thoughts?



I've been dedicating most of my time working on getting builds on Win32
running.  I know it isn't much and there are a lot of other stuff I was
hoping to do (particularly Sync).

I do apologize for the lack of updates; but, as it is, we're really
down in the resource department (particularly time and people).

I am, as I've posted, getting trunk and (hopefully) aurora nightlies
done consistently.  Then I'm doing the l10n repacks (nightly).
Once that can be consistently done, I'm going to do the release
when I have the necessary information.

I realize it's not the kind of update you're looking for, but those
are the steps that I need to do in order to get updates to release.

Thank you for everyone's patience.

Edmund
Thanks for all of your time and support Mr. Wong. It is truly 
appreciated by everyone in the SeaMonkey community. I have some down 
time this summer while I work for my College's computer science 
department, so I am hoping to contribute to the project if at all possible.

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

Re: How dead is SeaMonkey?

[John Duncan]

Paul B. Gallagher wrote:

Jonathan N. Little wrote:


Ray_Net wrote:


How can I change my UA string
from: Mozilla/5.0 (Windows NT 6.1; rv:35.0) Gecko/20100101 Firefox/35.0
SeaMonkey/2.32
to: Mozilla/9.0 (Windows NT 10.1; rv:99.0) Gecko/20100101 Firefox/99.0
?


You can either install an extension, there are several or in

about:config

edit or create string key if not present:

general.useragent.override


I'm curious -- I was browsing around looking at keys containing the
string "useragent" and came to one named

general.useragent.site_specific_overrides

Does that mean there's a way to lie to specific dysfunctional sites
while retaining the normal user agent string elsewhere?


Yes, from http://forums.mozillazine.org/viewtopic.php?f=40&t=2647781:

``Unfortunately some pages I must use are set to cooperate with 
"firefox" and IE only. I've managed with this:
1) by setting "general.useragent.site_specific_overrides" to TRUE (AFAIR 
it was default),
2) and adding "general.useragent.override.[site_address]" with value 
"Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/20100101 Firefox/18.0 
SeaMonkey/2.15.1".''

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

Re: How dead is SeaMonkey?

[John Duncan]

Ray_Net wrote:

Paul in Houston, TX wrote on 08/07/2015 01:08:

Ed Mullen wrote:

I've seen several sort of oblique mentions here of the lack of
development of SM.  Also,
haven't seen an update in a while.  So, I'm beginning to feel that
I'm nearing the point
where I cannot any longer stick with SM.

(snip)

Thoughts?


Why bother updating?
Just change your UA:
User-Agent: Mozilla/9.0 (Windows NT 10.1; WOW128; rv:99.0)
Gecko/20200101 Firefox/99.0


How can I change my UA string
from: Mozilla/5.0 (Windows NT 6.1; rv:35.0) Gecko/20100101 Firefox/35.0
SeaMonkey/2.32
to: Mozilla/9.0 (Windows NT 10.1; rv:99.0) Gecko/20100101 Firefox/99.0
?
user_pref("general.useragent.override", "Mozilla/9.0 (Windows NT 10.1; 
rv:99.0) Gecko/20100101 Firefox/99.0"); line in your user.js file should 
work. You can also add this in about:config with New->String and enter 
it there. This is the method that the add-on ``User-agent Switcher'' 
uses I believe.

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

Re: Again SeaMonkey is fully unknown

[John Duncan]

Daniel wrote:

On 8/07/2015 5:55 AM, John Duncan wrote:





To fix this,
couldn't we try always reporting the Firefox/x.x bit at the end of the
UA string to deal with invalid sniffing? or is that not the issue in
this circumstance?


Yes, you could, John, but then no-one will ever know about SM!! So you
might as well just use FF!

Ha, that is a good point! This doesn't really seem like a big issue 
anyway. I have yet to come across a website that denies me access based 
on the fact that I'm advertising SeaMonkey instead of Firefox. The 
``chrome-optimised'' websites on the other hand... *shudders*

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

Re: Again SeaMonkey is fully unknown

[John Duncan]

Daniel wrote:

On 8/07/2015 6:09 AM, John Duncan wrote:

EE wrote:

Daniel wrote:

and, Jonathan and others, just FYI, it's my belief that if the sniffers
sniffed for the term "Gecko" rather than the actual name then they
would
accept Firefox, SeaMonkey and Opera (and probably others), at a minimum


Opera uses Webkit, so why would a sniffer accept it by looking for
"Gecko"?


Probably because opera/chromium user-agents usually include the keywords
``Mozilla'' and/or ``KHTML, like Gecko'' somewhere in them.


Is that right, John?? Good, I was just about to reply to EE stating
that, "at first, I couldn't think of the third Browser so was going to
put "and some other browsers" in my reply, but then Opera popped into my
mind, so I stuck it in."

Yeah for me!!

Yes, I believe so. Although I have not used anything that's not based on 
Mozilla for awhile, it seems as if all modern versions of Opera 
advertise Mozilla/Gecko-compatibility in their UA simply for historical 
purposes (http://user-agents.me/search?q=32.0.1910.0). I know the older 
version either advertised the presto layout engine or Mozilla/Gecko. It 
also seems as if all versions of Google's chrome browser advertise 
``Mozilla/5.0'' and ``KHTML, like Gecko'' strings in its UA 
(http://user-agents.me/search?q=45.0.2438.3).

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

Re: "We plan to release SeaMonkey 2.35 asap in July."

[John Duncan]

Yamo' wrote:

Hi,

WaltS48 a écrit le 06/07/2015 15:49 :

Try 2.39a1 at the bottom of this page. [Index of
/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk](http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/)



I didn't found Lightlink version for 2.39 :


May I can  try 2.38a1?

Try out Lightning version 4.4-nightly from the [latest comm-central 
release](http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-comm-central/). 
I am using the most recent 2.39 comm-central build (from July 6th I 
believe) and have that version of Lightning installed. Works fine!

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

Re: How dead is SeaMonkey?

[John Duncan]

Paul in Houston, TX wrote:

cmcadams wrote:


I keep multiple partition backups on an external disk, and if
something happens,
usually because of something I did, I can revert without much angst.
Saves needing to
get fancy. I've never had anything get beyond a boot partition, that
I know of. But
if it did having the backups, plus something capable of rewriting
boot sectors,
should serve (he said, ever so confidently.) If not, there are always
flamethrowers
and holy water.

Should have mentioned that Adobe Acrobat is also a thing of the past,
and I keep my
Flashes locked down. No saving to disk, no sharing, no nothin' but
playing videos.
The three, Java, Adobe and Flash, seem to be the main players.


And Adblock Plus! Never ever forget that...


Almost the same for me.  Clone this hdd monthly then unplug the clone.
Back up & image the work computers monthly via usb.
Bluhell browser firewall, uBlock Origin, old Zone alarm firewall, two
hardware firewalls.
I don't remember what else...
I find the drama happening between the original ublock developer 
(gorhill) and the guy he gave the main repo to (chris) to be absolutely 
hilarious. never forget abp though. never thought that'd be considered a 
relic of the past.

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

Re: Again SeaMonkey is fully unknown

[John Duncan]

EE wrote:

Daniel wrote:

and, Jonathan and others, just FYI, it's my belief that if the sniffers
sniffed for the term "Gecko" rather than the actual name then they would
accept Firefox, SeaMonkey and Opera (and probably others), at a minimum


Opera uses Webkit, so why would a sniffer accept it by looking for "Gecko"?

Probably because opera/chromium user-agents usually include the keywords 
``Mozilla'' and/or ``KHTML, like Gecko'' somewhere in them.

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

Re: Again SeaMonkey is fully unknown

[John Duncan]

David E. Ross wrote:

On 7/5/2015 11:26 PM, Ray_Net wrote:

A site, telling me that my browser is not up-to-date direct me here:
http://browsehappy.com/?locale=fr

Where in cannot find SeaMonkey 



This is the result of invalid user-agent sniffing.  See my
.

Agreed. Perhaps, they are just sniffing the last string that is 
available in the useragent. For example, when I go to many of those 
``whatismyuseragent'' websites, they will truncate down my useragent 
into simply ``Lightning 4.4,'' because I am using the latest version of 
the Lightning calendar add-on which appends itself onto the end of my 
user agent string (after the SeaMonkey/2.xx bit). I am assuming it sees 
``SeaMonkey/2.xx'' or ``Lightning/4.4'' and assumes that you're using 
some ancient or non-existent non web-compliant browser. To fix this, 
couldn't we try always reporting the Firefox/x.x bit at the end of the 
UA string to deal with invalid sniffing? or is that not the issue in 
this circumstance?

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

Re: How dead is SeaMonkey?

[John Duncan]

Thee Chicago Wolf [MVP] wrote:

On Tue, 07 Jul 2015 16:07:19 +0200, Ray_Net
 wrote:


Thee Chicago Wolf [MVP] wrote on 07/07/2015 15:48:

On Tue, 07 Jul 2015 02:43:58 -0400, Ed Mullen 
wrote:


I've seen several sort of oblique mentions here of the lack of
development of SM.  Also, haven't seen an update in a while.  So, I'm
beginning to feel that I'm nearing the point where I cannot any longer
stick with SM.

Kind of sad since I've been with it since Netscape back in, about, 1995.
   I don't have any aversion to "an end of an era" but it would be nice
to get some definitive info on what the few remaining SM devs are doing
or have in mind.

Thoughts?

Well, new builds were supposed to be released end of June but that
date has come and gone. A few contrib builds has been built locally on
someone's machine
(https://blog.seamonkey-project.org/2015/06/16/first-win32-seamonkey-2-35-nightly-build-available/)
but we're all still waiting for a build server to be online and the
old build setup to be migrated. It's allegedly happening but very,
very, very slowly.

- Thee Chicago Wolf [MVP]

I think that users are more interested in solving unresolved bugs from
years and years then expecting design changes.


Nearly all the bugs fixed in FF and TB get pulled into SM.

- Thee Chicago Wolf [MVP]

True, which is very nice. A bit sad that Mozilla isn't ``innovating'' in 
Thunderbird anymore, but that is a discussion for another day. It is 
true that there are a few oddball seamonkey-specific bugs that are quite 
annoying, but I'm sure many will be getting fixed soon-ish. Honestly 
don't know what I would do if the SeaMonkey project ever died. Can't 
imagine using ANY other internet suite that could make me quite as happy 
or comfortable on the web. People like to rip on Mozilla for trying to 
stay marketable, but if it weren't for them, we would be dead in the 
water. Really appreciate how generous they've been to the SeaMonkey 
community the past ~10 years.

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

Re: Contributed or real version - definitions? --was [Re: "We plan to release SeaMonkey 2.35 asap in July."]

[John Duncan]

Daniel wrote:

On 6/07/2015 9:41 PM, Richard Owlett wrote:

Daniel wrote:

On 6/07/2015 5:36 PM, Yamo' wrote:

Yamo' a écrit le 06/07/2015 09:19 :


I didn't found any 2.35b1-candidates on :




Or alpha?


As SM 2.35 is going to be a Contributed Version (I think) rather
than a real version, I very much doubt there will be any Alpha's
or Beta's.



Definition of "Contributed Version" and "real version"?
TIA


Richard, as I understand things, the SeaMonkey Councils build machines
are broken so cannot produce "real" builds, so one or more of the
Council are producing builds on their private computers and letting
others use these contributed builds.

It's the same people doing the work, just QA, etc, may not be as thorough!


I thought it was only the windows build machine that went down?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey