Re: adblock ?

[Steve Dunn]

On 2021-02-01 04:07, rjkrjk wrote:

some websites I visit seem to indicate  Im suing some version of Adblock
and want me to update it, and allow me to continue

I check my Ad On Manger, there are no pgms installed


Some sites mistakenly interpret various forms of tracking protection as 
ad blocking.  Have a look at your privacy and cookie settings to see if 
you have any privacy measures set up that might be triggering these 
warnings.


Having said that, you may not be able to find a collection of settings 
that provides you with what you feel to be an acceptable level of 
privacy protection and yet is compatible with some of these sites.  You 
may have to set up a couple of browser profiles - one for general 
browsing, with privacy settings enabled, and another one with no privacy 
settings enabled so that you can browse these sites that have aggressive 
anti-adblocking measures in place.


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

Re: Does the Acrobat DC plug in no longer work in SM 2.53? Other broken helper apps

[Steve Dunn]

On 2020-05-25 21:09, Hawker wrote:

Since updating to SM 2.53 I'm having "helper app" issues.
The most annoying is that PDFs no longer open in the browser. Going to 
the helper app, I set it to open in SM or always ask but it stays on 
always ask. I seem to remember reading this this version was going to 
break a bunch of legacy plug ins. Could this be that?


	I can't say for sure but at some point (either 2.49 or 2.53; I don't 
recall which) I found that trying to view a PDF attached to an email 
would open a blank window.  If I close the window and try again, it 
works.  For me, it's an annoyance, but a minor one, so I'll deal with it.


Dunno if that information helps much, but at least it's another data 
point.

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

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

[Steve Dunn]

On 2020-03-14 20:40, Frank-Rainer Grahl wrote:

mozilla-lists.mbou...@spamgourmet.com wrote:
- There doesn't seem to be any problem setting a master password in 
2.53.1 once the profile has been converted.  Having done so, I assume 
it is actually encrypting the saved passwords (though it would be good 
to have that confirmed).


Yes and hopefully with better encryption.


	Thank you.  That answers the question that was not addressed by the 
release notes.


-Steve

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

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

[Steve Dunn]

On 2020-03-08 04:43, Daniel wrote:
If "I mostly use SeaMonkey for email and newsgroups" why not use 
Thunderbird in place of SeaMonkey?? That would save using resources on 
the unused Browser portion of SM!


	Eventually that will probably be necessary, but as long as SeaMonkey 
works, there's not much of a reason to bother migrating, especially as 
my computer is not short on resources.


-Steve

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

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

[Steve Dunn]

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

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


The most important ones for me are:

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

* HTTPS Everywhere 5.2.20

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


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

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

[Steve Dunn]

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


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


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

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

[Steve Dunn]

On 2020-03-05 15:17, Frank-Rainer Grahl wrote:
Check the password manager in the upgraded install. At least until 
recently this didn't work.


I tested only on Windows and left the new password blank e.g no chars 
entered. This worked fine for me.


	Can a master password be set after the upgrade has been completed, or 
must all saved passwords be left insecure until whenever this bug is 
fixed?  The release notes don't actually say - they just say you have to 
remove the master password before upgrading and them delete two files 
with unencrypted passwords in them after upgrading.


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

Re: Secure Connection Failed

[Steve Dunn]

On 2019-10-14 02:43, Ray_Net wrote:

An error occurred during a connection to www.seamonkey-project.org.

The OCSP server experienced an internal error.


	I've seen that error before, though only very infrequently.  I'm 
inclined to believe that it's exactly what the message says - a problem 
on the OCSP server.


	You could try fiddling with the OCSP preferences in SeaMonkey (Privacy 
& Security -> Certificates) to see if any of the settings let you get 
past this.


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

Re: All extensions allegedly broken under Firefox

[Steve Dunn]

On 2019-05-04 13:39, David E. Ross wrote:


SeaMonkey does not require extensions to be signed, at least in the
current end-user release 2.49.4.



	Which is largely a moot point since there have been few if any updates 
to most of these extensions for SeaMonkey's obsolete extension system 
for the last couple of years.


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

Re: Should the size of the memory cache be a setting in preferences?

[Steve Dunn]

On 2019-02-25 13:01, Dirk Munk wrote:
For many people the browser is their primary application, so making it 
run as smoothly as possible is quite a logical pursuit.


	Frankly, if a user's concern is having a browser that runs as smoothly 
as possible, SeaMonkey is not the right browser.  Despite spawning 
dozens of threads, it is quite poor at making use of multiple cores; I 
generally find that it won't use much more than one core's worth of CPU 
power (e.g. on a four-core system, the SeaMonkey process won't go much 
above 25% utilization), and so all it takes is one tab that's consuming 
CPU cycles to make the whole thing almost unresponsive.  (And yes, 
that's with a memory cache that I had increased from the default long 
ago.)  Firefox and Chrome both run rings around it in this department.


	That's one of the two main reasons I've largely (and reluctantly) 
abandoned SeaMonkey, the other being its archaic extension support that 
means none of the extensions I rely on have been updated in about a year 
and a half (and never will be).


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

Re: Should the size of the memory cache be a setting in preferences?

[Steve Dunn]

On 2019-02-25 08:09, Dirk Munk wrote:
However, there's also a memory cache in RAM, and the size of that cache 
can only be changed by tweaking the configuration file. I've noticed 
that increasing the memory cache can certainly increase the speed of 
Seamonkey, and can also avoid freezing problems etc.


	OK, I'll take the Devil's Advocate position against you :-)  And since 
you stated your qualifications, I'll mention that I have a degree in 
computer science and about 30 years of experience as a professional 
nerd, so you and I both have a good technical understanding to work from.


	Yes, increasing SeaMonkey's memory cache can improve performance - but 
it can also hurt system performance.  Most people run multiple programs 
at once, and if you set SeaMonkey to use lots of RAM, that means less 
RAM is available for other programs before the operating system has to 
start swapping, and as you know, once you start swapping, performance 
falls dramatically.  Even if your swap device is an SSD, it's still 
orders of magnitude slower than RAM.


	And sure, a 64-bit program has a massive virtual address space, and a 
64-bit operating system can access a lot of physical RAM, but I suspect 
most average users' PCs only have 4-8 GB of RAM.


	You and I have the technical background to understand that.  The 
average user doesn't.  Making this setting something that's exposed in 
the normal preferences menu rather than burying it in about:config 
invites users who don't have a technical background to make a bad 
choice.  So I think it's best left as is.  Users with technical skills 
can already easily change it (as you and I have both done).  Users 
without technical skills should not change it.


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

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Steve Dunn]

On 2018-12-24 20:02, Ray_Net wrote:
I totally agree with you, but do you think that a group of volunteers 
will be able to take this big step?


It doesn't sound promising, does it?

	But then again, I thought something similar when SeaMonkey 1.x kept 
dragging on with nothing but basically minor bug and security fixes for 
a couple of years before 2.0 was released ... and here we are nearly a 
decade later, with a SeaMonkey that still works on the vast majority of 
sites.  The team has done a heck of a job despite major challenges, so 
while I'm assuming I'll probably have to migrate off SeaMonkey at some 
point, I'm holding off on actually doing it for now.

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

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Steve Dunn]

On 2018-12-23 19:04, Nuno Silva wrote:

On 2018-12-22, user@domain.invalid wrote:

[...]  Because without an up to date engine Seamonkey
will not be able to appeal to new users and long time users will
slowly move on as well. I.e. in my optinion Seamonkey would not have a
future without an up-to-date engine.


Are you really sure nobody would be interested in Seamonkey if it does
not chase Firefox?


	It doesn't necessarily have to chase Firefox, but it has to be up to 
date.  Think back to when Seamonkey 1.x fell a couple of years behind 
Firefox while Seamonkey 2.x was in its prolonged gestation.  More and 
more sites didn't work properly in Seamonkey 1.x because it hadn't kept 
up with modern standards.  That's what's going to happen to Seamonkey if 
it doesn't get up to date.


	Maybe the best solution is the massive amount of work required to make 
Seamonkey compatible with a current version of Gecko (the engine it 
shares with Firefox).  Maybe the best solution is the massive amount of 
work required to rip Gecko out and replace it with something else 
(Chromium or WebKit or whatever).  Or maybe the best solution is 
something else.  But simply leaving it with the current engine is not a 
viable option; that will result in Seamonkey gradually becoming unusable 
as it gets left behind.

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

Re: "Updating everyone…" --SeaMonkey Project Blog on 12/19/2018...

[Steve Dunn]

On 2018-12-18 20:13, Ant wrote:

https://blog.seamonkey-project.org/2018/12/19/updating-everyone/


	Thank you to everyone who has been working on this project.  I 
understand that it's a huge task and the pay sucks :-) and I really do 
appreciate it.


	For what it's worth, here's my opinion on what I want to see in future 
Seamonkey, which may or may not be similar to anyone else's.  Executive 
summary:  my priorities for what I'd like to see in future Seamonkey 
versions are #1 support for non-obsolete extensions and #2 performance.


	Background:  Seamonkey is my default browser largely because I used 
Netscape, which morphed into Mozilla, which morphed into Seamonkey.  On 
my home computer, I also use it for personal email.  I also use Firefox 
and am quite happy with it; I just don't particularly want to have to 
switch (nor do I particularly want to have to switch my mail to 
Thunderbird), especially since I expect there would be quite a bit of 
the years worth of configuration (of the browser and of extensions) that 
might have to be redone by hand.


	The biggest thing I want Seamonkey to do is to support modern add-ons. 
None of the Seamonkey extensions I use have had updates in over a year; 
meanwhile, their Firefox versions continue to be developed.  So at some 
point, for me, Seamonkey becomes unusable as my main browser if things 
like ad blocking and HTTPS Everywhere are years out of date.


	#2 is performance.  I use both Seamonkey and Firefox on two different 
computers, and on both, Firefox performs better - sometimes dramatically 
so.  And any time Seamonkey is sluggish, the CPU utilization tells me 
it's largely running on one core only (e.g. it's eating about 25% of CPU 
time on a four-core computer), which usually isn't the case in Firefox. 
So I guess we need Quantum, and yes, I understand that's an enormous 
thing to port, but the farther Seamonkey falls behind other browsers in 
performance, the less useful it is.

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

Re: 32bit & 64bit SM questions.

[Steve Dunn]

On 2018-10-22 04:49, Daniel wrote:
FRG, I've seen "l10n builds", and the problems with it, mentioned for 
years. *What is it* ?? A Real World language?? A Programming language?? 
What??


	An abbreviation of localization.  The 10 stands for the ten letters 
left out between the l and the n.


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

Re: Wishlist of things I'd like to see

[Steve Dunn]

On 2018-06-25 00:04, Daniel wrote:

Steve, did you close the Browser or did you close SeaMonkey totally??


   I totally closed Seamonkey.  Anyway, since one of the developers has 
since posted that this preference has never done anything in the 
browser, now we know why it didn't work :-)


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

Re: Wishlist of things I'd like to see

[Steve Dunn]

On 2018-06-24 05:24, Daniel wrote:

sean wrote on 24/06/2018 7:49 AM:

browser.tabs.closeButtons;3

Sean according to 
http://kb.mozillazine.org/About:config_entries#Browser. you want that 
set to 1


	Unfortunately, that doesn't seem to work, at least in 2.49.3; I set it 
to 1, closed the browser, and restarted, but there is still just one X 
over on the right side.  It appears this behaviour is hard-coded.


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

Re: Disabling SSL/TLS protocols to safeguard payment data

[Steve Dunn]

On 2018-06-09 10:57, Richard Owlett wrote:

On 06/09/2018 09:29 AM, Steve Dunn wrote:

On 2018-06-08 15:02, Andy K wrote:
In about:config, set security.tls.version.min to 2 to prevent 
protocols lower than TLS 1.1 from being used.


 This is fine if you only use the browser to access sites that are 
compliant with payment industry standards.  But most people use 
browsers for more than just online banking etc., and some of those 
sites may not support newer TLS versions.


The vast majority of my transaction will be with my bank.
Is it reasonable to presume they will use the later standard?


	It should be, assuming that your bank takes PCI compliance seriously 
(and if they don't take industry security standards seriously, that 
should probably raise some other questions in your mind).  And if that's 
true, then you shouldn't need to disable TLS 1.0 on your browser to keep 
your banking data safe.  If the site you're connecting to only supports 
1.1 and 1.2, your browser can't negotiate 1.0 with them, unless there's 
a man-in-the-middle attack.


	For that matter, in the absence of a man-in-the-middle attack, your 
browser and the server should negotiate the highest mutually-supported 
TLS version.  So if your browser supports 1.0-1.2 (which I think is the 
default configuration for Seamonkey) and you're connecting to a site 
that supports 1.0 and at least one of 1.1 and 1.2, you shouldn't get 1.0.


	To be honest, I don't know how many sites still lack support for TLS 
1.1 or higher.  I have no doubt that there are some, either running 
outdated software or configured by administrators who don't know a lot 
about TLS versions, but have no idea if it's 0.001% or 1% or some other 
number.  You can always disable TLS 1.0, do your normal everyday 
activities for a while, and see if any of the sites you use break.


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

Re: Disabling SSL/TLS protocols to safeguard payment data

[Steve Dunn]

On 2018-06-08 15:02, Andy K wrote:

June 30, 2018 is the deadline for disabling SSL/early TLS and implementing a 
more secure encryption protocol – TLS 1.1 or higher (TLS v1.2 is strongly 
encouraged) in order to meet the PCI Data Security Standard (PCI DSS) for 
safeguarding payment data.

[...]

In about:config, set security.tls.version.min to 2 to prevent protocols lower 
than TLS 1.1 from being used.


	This is fine if you only use the browser to access sites that are 
compliant with payment industry standards.  But most people use browsers 
for more than just online banking etc., and some of those sites may not 
support newer TLS versions.  So just remember that after making this 
change, you will probably break your browser's ability to access some 
sites; you'll either need to keep switching your TLS minimum version 
back and forth, or use one browser for online banking etc. and a 
different browser for other activities.


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

Re: SeaMonkey version 2.49.3 Browser won't load Google and youtube sites

[Steve Dunn]

On 2018-05-22 07:04, dirk wrote:
I recently installed SeaMonkey version 2.49.3, but thr browser won't 
load Google and youtube sites, saying it is not safe


   It works for me.  When you look at the certificates, what's wrong 
with them?  Wrong site?  Wrong validity date(s)?  Are you, by any 
chance, using an Internet security program that messes with certificates 
(as some of them do) and requires you to install that program's 
certificate in your browser?


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

Re: SM 2.493 user name/passwords not remembered any longer

[Steve Dunn]

On 2018-05-17 09:07, rjkrjk wrote:

win7/64  6gb system

updated SM last night to 2.493

situation
signing in to ebay

typically I right click and the several accts that I have show up
NONE show up now

there seems to be a disconnect between the user names/passwords 
previously used with

SM 2.49


	I updated from 2.49.2 to 2.49.3 and have had no problems with my saved 
passwords.  I don't use ebay so I don't know if there's something 
specifically with that site; my passwords for lots of other sites all work.


What do you see when you look at ebay in Data Manager?

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

Re: Change User Agent for one domain only

[Steve Dunn]

On 2018-03-07 12:13, Hawker wrote:

I am currently using User Agent Switcher.


I've never used that extension so I can't help you with it.  But it's 
not the only way to fiddle with the user agent string.


What I mostly want to do is have all Google domain use default to the 
current FireFox UA as much of Google does not work properly with 
Seamonkey's UA but works fine when I switch it. I can't see how to lock 
that in with User Agent Switcher. I want everything else to default to 
Seamonkey.


In about:config, you can create per-domain/site custom user agents. 
Create a string named general.useragent.override.{domain} and set its 
value to the string you want.  For instance, if you want example.com to 
think your user agent is "Bogus/1.0 Fake/20180307" you'd create:


general.useragent.override.example.com = "Bogus/1.0 Fake/20180307"

Give it a shot and see if it helps.  It won't do anything for your 
second question since that involves easily switching user agents, but it 
might at least work for the first question.


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

Re: A question regarding junk mail

[Steve Dunn]

On 2017-12-13 18:48, Zeb Carter wrote:
I receive email from pensacon.com (sci fi convention is Pensacola, FL). 
Seamonkey thinks it's a scam or junk mail even though I do have the 
address in my addressbook (newslet...@pensacon.com). How do I get SM to 
stop flagging it? I hit the ignore warning button each time but I can 
get another one the next day and it gets flagged.


Two thoughts:

Do you have the setting turned on to trust messages from senders in your 
address book?  (Edit -> Mail and Newsgroup Account Settings -> {the 
account) -> Junk Settings)?


Seamonkey's junk controls are inadequate - the Junk and Not Junk buttons 
don't appear everywhere they're needed.  I use an add-on called 
JunQuilla to allow better management of the junk mail filters.


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

Re: SeaMonkey 2.49.1 (Windows) freezes

[Steve Dunn]

On 2017-12-02 21:03, NoOp wrote:

Have anyone else had SM 2.49.1 (Windows) freeze on them?


   I haven't had this problem.  Like you, I'm using the same profile 
I've been using for years.  Unlike you, I haven't used any pre-release 
(alpha, beta, dev, whatever) versions and then gone back down a couple 
of versions to a release version; I got to 2.49.1 from 2.48.  I can't 
say that's the problem but it does seem like a possibility that 
something in your profile got out of whack when you came back from the 
future :-)


   If you're interested in troubleshooting it, a couple of options come 
to mind:  see if you can duplicate it in safe mode, and see if you can 
duplicate it after creating a fresh new profile.  I'd suggest backing up 
your profile before either of these, just to be on the safe side.  Post 
again with the results and that might help some of the gurus track down 
what's going on.

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

Re: There's a "video war" going on, and we users are the victims

[Steve Dunn]

On 2017-08-22 10:20, null wrote:

WaltS48 wrote:

Do you have HTML5 support?



What is checked there?


Using SM, The page asks the question "What does this browser support?"

The following boxes are ticked :
HTMLVideoElement
Media Source Extensions
WebM VP8
MSE & WebM  VP9

The following boxes have an exclamation mark in them :
H.264
MSE & H.264

Do I have HTML5 support? From the above, I'm unclear.


	You do, but you are missing one of the most common codecs, which may be 
the problem.  There are numerous codecs (COmpressors-DECompressors) for 
video, much like there are for audio, and you need to have at least one 
in common with whatever codecs the site you're visiting supports.


	To put it in a non-technical analogy, HTML5 support is like the Roman 
alphabet and the codecs (VP8, VP9, H.264, etc.) are like languages.  If 
I know the Roman alphabet and two languages that use it (say, English 
and French) but the site only has videos in two other languages that 
also use the Roman alphabet (say, Swedish and Romanian), well, that 
won't work.


	My 32-bit Seamonkey 2.46 running on 64-bit Windows 7 has checkmarks in 
all of those boxes, and has no problem playing videos on Youtube.  That 
does lend credence to the theory that it's because you're missing H.264.


	Years ago, I saw a recommendation for the K-Lite Codec Pack and I 
installed it on my computer.  Maybe that's the difference.


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

Re: No more plugin check?

[Steve Dunn]

On 2017-08-03 04:17, Paul B. Gallagher wrote:


doesn't check plugins anymore, just promotes Firefox.


Firefox removed the link to that page on their about:plugins page a few 
versions ago.  I'm not surprised if this page no longer works properly 
since Firefox no longer uses it.


-Steve

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

Re: How to disable HTML5 auto play?

[Steve Dunn]

On 2017-08-02 08:45, Ray_Net wrote:

I had under 2.46 disbabled the auto-play .. AND the result is : When I
try to start the video ... NOWAY ! the video would not start - never 


I have the same experience.  If autoplay is disabled, at least some 
videos will not start even when you click play.


I don't believe I have the same problem in Firefox - I have autoplay 
disabled there and yet videos do start when I want them to.  So this 
undesirable behaviour seems to be a Seamonkey thing.

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

Re: adblocker in Seamonkey automatically

[Steve Dunn]

On 2017-07-27 09:33, Gerd Schweizer wrote:

Is ist possible, that there is an automatic Adblocker in Seamonkey 1.46?
Why i ask is:
There is a way to get Navi updates from the server of an automobile
firm. Their Website tells me, the download is finished even though
nothing has happened.


No, which is why so many of us use add-ons like Adblock Plus.  But 
there's a pop-up blocker, and some download sites require pop-ups for 
downloads.  Try turning it off (Edit -> Preferences -> Privacy & 
Security -> Popup Windows) and see if that makes a difference.


Also, check your download settings (Edit -> Preferences -> Browser -> 
Downloads) to make sure that you'd actually see if a download starts, 
because there are settings that can make downloads happen with or 
without various types of notifications.


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

Re: Facebook Login

[Steve Dunn]

On 2017-07-14 11:09, Tom Pamin wrote:

All of a sudden, I have to login to Facebook with SM 2.46 every time I
turn on my PC or laptop. Never had to before - I was already logged in.
Any ideas?


Did you change your cookie permissions?  I'd expect that Facebook, like 
other sites, stores a big pile of cookies in your browser, and if you've 
changed a browser setting that causes your browser to delete these 
cookies when it's closed, or after a very short period of time, Facebook 
will make you log in again.


Have a look at what permissions you're using for Facebook (e.g. see 
what's indicated when you pick Tools -> Cookie Manager while on 
Facebook, or Tools -> Cookie Manager -> facebook.com -> Permissions); or 
close Seamonkey, open it, and then (without attempting to log into 
Facebook or do anything else) look to see whether you have stored 
cookies from Facebook (Tools -> Cookie Manager -> facebook.com -> 
Cookies, or chrome://communicator/content/permissions/cookieViewer.xul).


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

Re: WYSIWYG printing?

[Steve Dunn]

On 2017-03-05 01:02, Paul B. Gallagher wrote:

Many website nowadays have their own "Print" buttons that deliver what
the designers consider "printer-friendly" versions of their pages. But
even if I ignore those and use SeaMonkey's own "Print" function, many
sites outsmart me by serving their "printer-friendly" versions. A prime
example is . Pick any page and print it, and
you'll find that you've lost all the graphics, fonts, and layout and
gotten only a plain-text version of the page.


	Others have responded with suggestions, but here's one part that hasn't 
come up yet.


	HTML style sheets can be tailored for various media, as the author of a 
page may wish to tailor it to different devices (including things like 
screens, printed output, and even screen readers that speak the contents 
of the page for the visually impaired).  If you look at the HTML source 
for an NY Times article, you'll find it lists multiple style sheets, and 
one of them will be for print.  Here's an excerpt from the source from a 
semi-randomly chosen article on their site:


link rel="stylesheet" type="text/css" media="print" 
href="https://a1.nyt.com/assets/article/20170302-131745/css/article/story/styles-print.css;


	So the article itself specifies a different style sheet for printing. 
Your browser is just following the instructions in the HTML, as 
standards say it should.

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

Re: Security warning - want to turn it off.

[Steve Dunn]

On 2017-02-22 09:56, JAS wrote:

Should a person have TLS 1.0 checked or not?


In an ideal world, off, as TLS 1.0 has known security problems.

	In the real world, though, you'll probably find that you can't connect 
to some sites if this is off; there are still some older Web servers out 
there that simply don't support 1.1 or later, and there are likely some 
which have it disabled by the administrator.

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

Re: Security warning - want to turn it off.

[Steve Dunn]

On 2017-02-22 02:02, Paul in Houston, TX wrote:

I happens when I enter a zip code in the location box at:
https://radar.weather.gov/radar.php?rid=hgx=N0R=yes


	It's exactly what the warning message says it is:  anything you enter 
in this form gets sent back to the server unencrypted.  Here, stripped 
of some markup, is the key part of the HTML source code for that form:


form method="POST" action="http://forecast.weather.gov/zipcity.php;

	Note that the action to send your input to the server uses http, not 
https.  That's why you get the warning.

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

Re: SSL_ERROR_NO_CYPHER_OVERLAP on videosift.com web site

[Steve Dunn]

On 2017-01-26 03:12, Ant wrote:

As you guys know, both Gecko based web browsers are the (lat/new)est
stable versions which I told them. "Can't they be made to also support
modern protocols?" is what they asked. So, I am asking you guys on how
to resolve/fix this security connection issue.


There are a lot of pieces to the puzzle here.  Each side supports 
various combinations of SSL/TLS versions, cipher suites, and so on - and 
in many cases the software allows the administrator/user to enable or 
disable parts of it.  I may speak ten languages and you may speak 
twenty, but if we have no languages in common, we can't have a 
conversation.  The same applies to SSL/TLS.


I'm glad to see that it got sorted out this time; it sounds like they 
made a configuration error when they were trying to improve security. 
If you run into this sort of thing in future and want some 
troubleshooting info, try these two steps:


1.  Go to https://www.ssllabs.com/ssltest/index.html and have it test 
the site that's giving you problems


2.  Go to https://www.ssllabs.com/ssltest/viewMyClient.html - this will 
tell you what parameters your browser supports


The first one includes simulation of various browsers to show whether 
that browser can connect to the site and, if so, what parameters would 
be used.  It doesn't include Seamonkey but it does include a few Firefox 
versions so you may find your answer in there without even resorting to 
step 2.  (I believe it simulates default settings only, so if you've 
fiddled with some of your settings, you may get a different result than 
the test does even if you're using exactly the same browser version.)


Failing that, comparing the list of what parameters the site supports 
from step 1 and what parameters your browser supports from step 2 will 
often show that there's a mismatch which prevents communications.

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