Re: Is anyone else having problems playing Brightcove.net's videos?

[Daniel]

On 30/10/2016 3:35 PM, Paul B. Gallagher wrote:

Ant wrote:


For an example with


... Video doesn't play. I tried a brand new SM profile too.

Thank you in advance. :)


Yep, same here. Clicked "play," nothing happened.


After a minute or so, my screen showed

"Could not download the video
Error Code: PLAYER_ERR_TIMEOUT"

My Win7 dialing agent showed that I had d/l'ed some data, but nothing 
showed!


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

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

Re: Is anyone else having problems playing Brightcove.net's videos?

[Desiree]

On 10/29/2016 4:52 PM, Ant wrote:

For an example with
http://players.brightcove.net/4221396001/V19oeQPdg_default/index.html?videoId=5189738190001
... Video doesn't play. I tried a brand new SM profile too.

Thank you in advance. :)

Agreed.  Even on a new profile I get a blank page for your url. 
However, a new profile for Fx 45.4 ESR DOES play that video just fine. 
(The default FX profile won't play it.  Default profile on Pale Moon 
won't play it and I didn't try a newer profile).


(I think the cat was just reaching for the toddler's leg as a moving 
object that went past it.  I don't think it was "tripping" the toddler).

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

Re: Is anyone else having problems playing Brightcove.net's videos?

[Paul B. Gallagher]

Ant wrote:


For an example with

... Video doesn't play. I tried a brand new SM profile too.

Thank you in advance. :)


Yep, same here. Clicked "play," nothing happened.

--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

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

Re: Chase Bank doesn't like SeaMonkey

[David E. Ross]

On 10/29/2016 7:39 PM, JAS wrote:
> J. Weaver Jr. wrote:
> 
>>
>> In a browser page address bar, type "about:config" (without the quotes).
>>
>> Anywhere in the body of the page, right click, select "New" and "String".
>>
>> At the "Enter the preference name" prompt, type
>> "general.useragent.override.chase.com" (without the quotes).
>>
>> At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0)
>> Gecko/20100101 Firefox/43.0" (again, without the quotes).
>>
>> Many other user agent strings will also work, but that one's working for
>> me.  -JW
> I thought that the general.useragent.override did not work anymore? At 
> least it does not for me.
> 

When I use the PrefBar extension to spoof a different browser, the
preference variable general.useragent.override -- the same one you cite
-- is what gets set.  I tested it at two Web pages, and it does work.

The two test pages are:

*  My own .  You can
see your own UA string under the entry for "UA".  Note that two UA
strings are shown there: my default UA string back in 2014 (when I last
updated the page) and any visitor's current UA string.

*  Panopticlick at .  After Panopticlick
did its analysis, I had to ask it for details.  The UA string appeared
near the bottom of the list of details.

If you manually edit prefs.js while SeaMonkey is an active application
(even if it is idle) rather than using about:config, it will not be
effective.  The prefs.js file on disc is read when SeaMonkey is
launched.  Thereafter, only the in-memory copy is used.  Furthermore,
the in-memory copy is then written over the disc file when SeaMonkey is
terminated.  In other words, DO NOT MANUALLY EDIT prefs.js.  (There is
an exception when moving the location of a SeaMonkey profile, either to
a different disc location or to a different computer.)

My preferred methods of changing preferences are, from most to least
preferred:
*  [Edit > Preferences] on the SeaMonkey menu bar
*  An extension, especially PrefBar
*  editing the file user.js, which requires SeaMonkey to be terminated
and then re-launched to become effective
*  about:config (generally only for testing a preference change)

The above is based on my experience with a major computer system used by
the U.S. military to operate its space satellites.  Part of my task was
to train U.S. Air Force officers on how to use the system.  I always
emphasized that changes to system controls were best done by using the
available user-oriented applications for that purpose instead of trying
to tweak the controls via the database system.  That ensured all
subsidiary changes related to the primary change -- many of which were
not obvious -- were also done because they were built into the
user-oriented applications.

The last time I edited the prefs.js file was in 2013, when my Windows XP
PC died and I had to rehost SeaMonkey on a Windows 7 PC.  Fortunately,
the hard drive containing my data (including my SeaMonkey profiles)
could be read by the new PC.

-- 
David E. Ross

Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[JAS]

JAS wrote:

J. Weaver Jr. wrote:



In a browser page address bar, type "about:config" (without the quotes).

Anywhere in the body of the page, right click, select "New" and "String".

At the "Enter the preference name" prompt, type
"general.useragent.override.chase.com" (without the quotes).

At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0)
Gecko/20100101 Firefox/43.0" (again, without the quotes).

Many other user agent strings will also work, but that one's working for
me.  -JW

I thought that the general.useragent.override did not work anymore? At
least it does not for me.

Nix my last reply as it does work and I had misspelled the word 
override. My bad.


--
   You either teach people to treat you with dignity and respect, or 
you don't. This means you are partly responsible for the mistreatment 
that you get at the hands of someone else.

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

Is anyone else having problems playing Brightcove.net's videos?

[Ant]

For an example with 
http://players.brightcove.net/4221396001/V19oeQPdg_default/index.html?videoId=5189738190001 
... Video doesn't play. I tried a brand new SM profile too.


Thank you in advance. :)
--
"I got an ant farm; them fellas didn't grow sh*t." --Mitch Hedberg
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
  / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net
 | |o   o| |
\ _ /If crediting, then use Ant nickname and AQFL URL/link.
 ( )   Axe ANT from its address if e-mailing privately.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[JAS]

J. Weaver Jr. wrote:



In a browser page address bar, type "about:config" (without the quotes).

Anywhere in the body of the page, right click, select "New" and "String".

At the "Enter the preference name" prompt, type
"general.useragent.override.chase.com" (without the quotes).

At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0)
Gecko/20100101 Firefox/43.0" (again, without the quotes).

Many other user agent strings will also work, but that one's working for
me.  -JW
I thought that the general.useragent.override did not work anymore? At 
least it does not for me.


--
   You either teach people to treat you with dignity and respect, or 
you don't. This means you are partly responsible for the mistreatment 
that you get at the hands of someone else.

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

64 Bit SeaMonkey Page Reload Problem

[Big Jim]

A few days ago I updated SeaMonkey to 64 bit.
I like the 64 bit browser but in both Version 2.45 and 2.46 I have found 
that I cannot reload a page by clicking on "Reload" or by pressing F5. 
If I hold down "Control" and click "Reload" the page will reload in a 
new tab.  If I try this with F5 nothing happens.  The only way that I 
have found to reload a page in the same tab is by clicking it in the 
navigation frame and hitting "Enter".
This only happens in the SeaMonkey browser and I did not have the 
problem using 32 bit.

Has anyone else seen this?  Is there a work around?
Thanx!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: A visual aid for tri-focal generation - Available? Feasible?? Bottom posting...

[Harsha Godavari]

The quoted message was more than 2 -screens full and the response was one line! 
Does this really justify "Tradition"? 

- Original Message -

From: "Ray_Net"  
To: support-seamonkey@lists.mozilla.org 
Sent: Saturday, October 29, 2016 7:48:12 PM 
Subject: Re: A visual aid for tri-focal generation - Available? Feasible?? 

Richard Owlett wrote on 28-10-16 19:46: 
> On 10/28/2016 10:39 AM, Ray_Net wrote: 
>> Richard Owlett wrote on 26-10-16 22:25: 
>>> On 10/26/2016 1:41 PM, G. Ross wrote: 
 Richard Owlett wrote: 
> I'm a tri-focal wearer with a fussy and strong astigmatism. 
> I have problems spotting the microscopic image which tags a 
> folder with *NEW* unread messages. Messages in folders keep 
> their 
> status as "unread" until I deal with the contents - it's 
> essentially my to-do list. I use flag status for a different 
> function. 
> 
> I am using SeaMonkey 2.40 on WinXP Pro SP3 
> My likely relevant settings are: 
> View->Layout->Classic View 
> View->Apply Theme->SeaMonkey Default Theme 
> 
> My preferred solution would be to change the color of the folder 
> title to indicate presence of *NEW* unread messages. 
> A _possible_ alternative might be toggling font face/metric of 
> the folder title. 
> 
> Comments? 
> TIA 
> 
 Instead of re marking it as unread, you can right click on the 
 heading and select "tag". This gives you a range of types of 
 tags with different colors. I have never used it except to try 
 it out. Try that out. 
 
>>> 
>>> I already have 26 tags defined. Some based on subject. Some 
>>> based on importance. Some messages have 3 or 4 tags applied. 
>>> Under Views->Message->Custom Views I have 14 listed. I also 
>>> display the total number of unread messages in each folder so 
>>> it seems reasonable to wish change some *VISIBLE* attribute of 
>>> the folder's name when there is a *NEW* message present. Rather 
>>> than that all but infinitesimal microscopic arrow. 
>>> 
>>> YMMV ;/ 
>>> 
>> Perhaps the best way is to "move" the message into the well 
>> choosen folder name into the "Local Folders" groups. 
> 
> That would obscure important context information i.e. which post of 
> which sub-thread it refers. It's not unusual for someone to reply to 
> multiple posts by one author - those posts being in distinct sub-threads. 
> 
> 
You are too complicated  I give up :-) 
___ 
support-seamonkey mailing list 
support-seamonkey@lists.mozilla.org 
https://lists.mozilla.org/listinfo/support-seamonkey 

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

Re: Can't fullscreen with YouTube's HTML5 videos ...

[EE]

Paul B. Gallagher wrote:

EE wrote:

Paul B. Gallagher wrote:

Ant wrote:

On 10/27/2016 10:08 PM, Paul B. Gallagher wrote:

Ant wrote:

Hi.

I'm getting used to HTML5 videos since I can use SM's about:config's
autoplay off value instead of having to use Flash to activate to
show on
my new 64-bit W7 EE SP1 installation. However, I am having problems
with
YouTube's HTML5 videos to go fullscreen. YouTube's greyed out
fullscreen
icon option's link goes to
https://support.google.com/youtube/answer/6276924 ... It says "On
Firefox, try the following steps: In the location bar (where you
enter
URLs), type "about:permissions" and hit enter." However, SeaMonkey
v2.40
doesn't have it.

How can I get to there with "You'll see a Fullscreen setting. Select
'Always ask' or 'Allow' to allow YouTube to go fullscreen on these
sites." instructions? I tried SM's Data Manager and looking in
youtube.com domain, but did not see any full screen.

Thank you in advance. :)


An easy workaround that you can turn on and off on the fly is to hide
the location bar (click the speckly rectangle to the left of it)
before
toggling full screen. When you exit full screen with ESC or whatever,
reveal the location bar the same way.


If you mean the toolbar's URL form on the top of SM between its menu
and
bookmarks, then it didn't work.


OK, well, it works here. I went to YouTube, hid what SM calls the
"navigation toolbar," started a video, clicked the maximize button in
the lower right corner of the vid, and got a true full-screen video
without anything but the video itself.


I simply set full-screen-api.enabled to true.  I get full-screen with
only the video on the screen.


I have that setting, too. Don't remember when I did it.

But if I don't hide the navigation toolbar myself, it remains visible
when I choose full screen.


With videos in full screen, I do not see the navigation toolbar.

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

Re: Migrating SM from WinXP to Win7

[EE]

Alexander Yudenitsch wrote:

I'm currently migrating from using SM on WinXP to a XP/7 dual-boot
system, so my query has two 'prongs':  Migrating SM from WinXP to Win7,
and saving information from a previous profile to a new one (which I'm
sure is a devious and tricky one, since I'm after specific details, and
not generic advice, and realize there may not be anyone with such advice
available here when I write).

I know that, if you leave a SM Profile after uninstalling the SM
program, when you reinstall it, this Profile is recognized by the
installation, and SM is installed ready to continue using the Profile --
That works fine if you're using the same OS for both installations, or
if both OS's have the same directory structure:  E.g., when going from
Win2K to WinXP, there's no (or minimal) need to adjust anything, since
both have practically the same file structure and names (besides the
"WINXP/WINDOWS" change); however, since XP and W7 use quite different
file structures and names, I'm stumped about how to use this 'natural
migration' which SM tends to use.

Just to what happens, I installed the same SM version I have on XP to a
W7 'temporary install', and saw that files are assigned to W7
(sub-)directories which don't even exist in XP, and am uncertain if I'll
know where my existing profile files would go (I imagine I'd have to
manually edit some .INI and .JS files to reflect these changes -- but,
again,from what to what?  Where can I find this correspondence?

The other part of the problem is that I've been migrating/evolving this
Profile since 1995, using Netscape, then MozSuite, and now SM,
installing and uninstalling many add-ons/extensions over time, so there
must be lots of unnecessary and/or problematic data left behind, because
sometimes uninstalling doesn'1t clear the add-on's data.

I'm ready to 'start from scratch' and reinstall all extensions, but want
to keep my 'history' -- which, since it's been incorporated into
"places.sqlite", is sort of a "black box", so I don't know how I can
'migrate' it after a clean uninstall.

I'm not sure if the above is enough to describe the problem, but so far
I'm between two unsatisfactory options:  Leave all the data from my
current profile when I install SM on W7 (I presume it's possible to
determine exactly where each file 'should' go), and try to clear up
what's possible without risking the current data; OR, make a clean
install, and then migrate the add-ons data (including "places.sqlite")
to the new Profile, which seems to have a high probability of making the
Profile unusable!

An added problem is that, for many months now, I've been having more and
more problems with javascript in SM (at least, it seems to be JS:  I
installed FireFox for comparison, and that install seems to have copied
much of he SM options, but still the same sites don't have the JS
problems, while they do in SM), but I think it's best to leave that
aside for now, and maybe open a new thread for this, unless someone says
it's directly related to the migration/data problem I described above.


You could let SeaMonkey set up a new profile and then dump the contents 
of the old profile into the new one.  You might have to change a few 
pathnames in the settings afterwards.


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

Re: A visual aid for tri-focal generation - Available? Feasible??

[Ray_Net]

Richard Owlett wrote on 28-10-16 19:46:

On 10/28/2016 10:39 AM, Ray_Net wrote:

Richard Owlett wrote on 26-10-16 22:25:

On 10/26/2016 1:41 PM, G. Ross wrote:

Richard Owlett wrote:

I'm a tri-focal wearer with a fussy and strong astigmatism.
I have problems spotting the microscopic image which tags a
folder with *NEW* unread messages. Messages in folders keep
their
status as "unread" until I deal with the contents - it's
essentially my to-do list. I use flag status for a different
function.

I am using SeaMonkey 2.40 on WinXP Pro SP3
My likely relevant settings are:
View->Layout->Classic View
View->Apply Theme->SeaMonkey Default Theme

My preferred solution would be to change the color of the folder
title to indicate presence of *NEW* unread messages.
A _possible_ alternative might be toggling font face/metric of
the folder title.

Comments?
TIA


Instead of re marking it as unread, you can right click on the
heading and select "tag".  This gives you a range of types of
tags with different colors.  I have never used it except to try
it out.  Try that out.



I already have 26 tags defined. Some based on subject. Some
based on importance. Some messages have 3 or 4 tags applied.
Under Views->Message->Custom Views I have 14 listed. I also
display the total number of unread messages in each folder so
it seems reasonable to wish change some *VISIBLE* attribute of
the folder's name when there is a *NEW* message present. Rather
than that all but infinitesimal microscopic arrow.

YMMV ;/


Perhaps the best way is to "move" the message into the well
choosen folder name into the "Local Folders" groups.


That would obscure important context information i.e. which post of 
which sub-thread it refers. It's not unusual for someone to reply to 
multiple posts by one author - those posts being in distinct sub-threads.




You are too complicated  I give up :-)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Felix Miata]

NFN Smith composed on 2016-10-29 10:17 (UTC-0700):


Felix Miata wrote:



...automate...



...user.js...


only
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[David E. Ross]

On 10/29/2016 8:58 AM, Felix Miata wrote:
> NFN Smith composed on 2016-10-29 08:41 (UTC-0700):
> 
>> Thus, your choices for that are either hard-coding into prefs.js (which
>> you'll need to remove when you upgrade Seamonkey), or using one of the
>> extensions noted here.
> 
>> However, when you resort to spoofing you do have do a little maintenance
>> work, because Firefox versions are a constantly moving target. If you
>> hard-code into prefs.js, then you'll probably want to remove that
>> setting, when the next version of Seamonkey is released.
> 
> One should only ever manipulate prefs.js manually in the most extreme of 
> circumstances, and only with knowledge of the consequences. The right way to 
> automate inclusion of a prefs override is via user.js, a purely optional 
> profile file that SM will only read from, never write to.
> 
> http://kb.mozillazine.org/User.js_file
> 

Another reason to use user.js is that comments can be inserted into the
file to remind the user why a preference change has been inserted.
Other than the standard comment -- warning users not to manually edit
prefs.js -- comments cannot exist in prefs.js.

-- 
David E. Ross

Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[NFN Smith]

Felix Miata wrote:


One should only ever manipulate prefs.js manually in the most extreme of
circumstances, and only with knowledge of the consequences. The right
way to automate inclusion of a prefs override is via user.js, a purely
optional profile file that SM will only read from, never write to.

http://kb.mozillazine.org/User.js_file



Right.  Either user.js, or adding the necessary preference via about:config.

Smith

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

Re: Chase Bank doesn't like SeaMonkey

[Felix Miata]

NFN Smith composed on 2016-10-29 08:41 (UTC-0700):


Thus, your choices for that are either hard-coding into prefs.js (which
you'll need to remove when you upgrade Seamonkey), or using one of the
extensions noted here.



However, when you resort to spoofing you do have do a little maintenance
work, because Firefox versions are a constantly moving target. If you
hard-code into prefs.js, then you'll probably want to remove that
setting, when the next version of Seamonkey is released.


One should only ever manipulate prefs.js manually in the most extreme of 
circumstances, and only with knowledge of the consequences. The right way to 
automate inclusion of a prefs override is via user.js, a purely optional 
profile file that SM will only read from, never write to.


http://kb.mozillazine.org/User.js_file
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[NFN Smith]

Marisa Ciceran wrote:

I have been a faithful user of Seamonkey and its predecessors since the
mid-1990s. Have there been no updates to Seamonkey since the release of
version 2.40 in March 2016?



That's correct.


It is for months that I have been unable to log into my Chase bank
accounts because chase.com claims that Seamonkey is out of date.  I know
that there have been extensive discussions on this chronic problem, but
since I am not a programmer I have not been able to decipher from the
various threads whether or not a viable solution has been found. The
suggestions to change banks or stop using Seamonkey are not reasonable
options to me.


Or, another option would be to use another browser just for Chase. 
There's nothing that requires you to commit exclusively to a single browser.


However, judging by reports in this newsgroup, there seems to be an 
increasing number of sites that are complaining about Seamonkey. If you 
have the setting for Firefox compatibility enabled (and I don't remember 
where it is, at the moment), Seamonkey 2.40 advertises that it's Firefox 
43.0. Although Chase has had historic problems with demanding Firefox 
(and ignoring other Gecko browsers), I think the complaints are more 
from sites that object to Firefox 43, rather than Seamonkey.


Back in July, I did some testing with Seamonkey and Chase, and noting my 
results in a couple of messages that I posted to a similar discussion in 
this newsgroup.


I'll re-iterate highlights here:




I ran a some tests at https://chaseonline.chase.com, using both spoofing from 
PrefBar, as well as installed browsers. I found:

1) If I try a login with a standard Seamonkey Profile (and default user agent 
strings), Chase complains about my browser. UA string that I used is: 
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 
SeaMonkey/2.40

2) Using PrefBar to spoof, I have no problem logging in, if the UA is showing:

* default Firefox:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0

* Chrome:

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/49.0.2623.87 Safari/537.36

* Opera

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/49.0.2623.75 Safari/537.36 OPR/36.0.2130.32


3) I also found that when I am spoofing, after I get past the login dialog, I 
can change the UA back to the Seamonkey default, and there's no apparent 
problems with further access.

4) I tried a login with PaleMoon 32,, and found no problems with login.

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/49.0.2623.87 Safari/537.36



I also noted in a separate reply:




How does one go about changing the user agent string in SM2.40?
Could not easily find that information.


There's a couple of ways, as noted elsewhere in this thread.

1) You can do it permanently, via changes in prefs.js:

J. Weaver Jr. noted:


"about:config",

create string "general.useragent.override.chase.com"

set it to your current useragent string _without_ the "SeaMonkey".
(mine is "Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101
Firefox/43.0")


2) Use an extension, either PrefBar or UserAgentSwitcher.
Personally, I prefer PrefBar, partially because it seems easier to use,

> and partly, because I like some of the other options offered, of
> getting to preferences quickly.


I do know that with PrefBar, the default strings offered are *very*
old, and you generally have to go in and edit to match something
reasonably current. I'm currently using:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0


Since that posting, I've updated my spoofing string to use:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0


I suspect that when Seamonkey 2.46 comes out and the string used by 
advertising "Firefox compatibility" is upgraded, the growing number of 
Seamonkey conflicts will go away.  Until then, you'll have to do the 
compatibility settings yourself, to make sure you're advertising a more 
current version of Firefox.


Thus, your choices for that are either hard-coding into prefs.js (which 
you'll need to remove when you upgrade Seamonkey), or using one of the 
extensions noted here.


However, when you resort to spoofing you do have do a little maintenance 
work, because Firefox versions are a constantly moving target. If you 
hard-code into prefs.js, then you'll probably want to remove that 
setting, when the next version of Seamonkey is released.


Smith


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

Re: Chase Bank doesn't like SeaMonkey

[WaltS48]

On 10/29/2016 11:20 AM, David E. Ross wrote:

On 10/29/2016 5:11 AM, Marisa Ciceran wrote:

I have been a faithful user of Seamonkey and its predecessors since the
mid-1990s. Have there been no updates to Seamonkey since the release of
version 2.40 in March 2016?

It is for months that I have been unable to log into my Chase bank
accounts because chase.com claims that Seamonkey is out of date.  I know
that there have been extensive discussions on this chronic problem, but
since I am not a programmer I have not been able to decipher from the
various threads whether or not a viable solution has been found. The
suggestions to change banks or stop using Seamonkey are not reasonable
options to me.

Can anyone please give this and other non-techie users a clue on the
status of this issue? I would appreciate it.

Thank you.

Marisa



I much prefer waiting for new versions than the every-6-weeks new
versions pushed for Firefox.

As for Chase Bank, the problem is with the bank and not SeaMonkey.
Chase's Web server simply rejects SeaMonkey.  However, you can always
have SeaMonkey make Web servers think you are using Firefox.  Several
suggestions on how to do this have already been made in this discussion.
  Also previously suggested is that you change to a bank that does not
discriminate against SeaMonkey.




Well, SeaMonkey is supposed to follow the Firefox release schedule, but 
they keep having problems getting them to build.



--
Visit Pittsburgh 
Coexist 
National Popular Vote 
Ubuntu 16.04LTS
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[David E. Ross]

On 10/29/2016 5:11 AM, Marisa Ciceran wrote:
> I have been a faithful user of Seamonkey and its predecessors since the 
> mid-1990s. Have there been no updates to Seamonkey since the release of 
> version 2.40 in March 2016?
> 
> It is for months that I have been unable to log into my Chase bank 
> accounts because chase.com claims that Seamonkey is out of date.  I know 
> that there have been extensive discussions on this chronic problem, but 
> since I am not a programmer I have not been able to decipher from the 
> various threads whether or not a viable solution has been found. The 
> suggestions to change banks or stop using Seamonkey are not reasonable 
> options to me.
> 
> Can anyone please give this and other non-techie users a clue on the 
> status of this issue? I would appreciate it.
> 
> Thank you.
> 
> Marisa
> 

I much prefer waiting for new versions than the every-6-weeks new
versions pushed for Firefox.

As for Chase Bank, the problem is with the bank and not SeaMonkey.
Chase's Web server simply rejects SeaMonkey.  However, you can always
have SeaMonkey make Web servers think you are using Firefox.  Several
suggestions on how to do this have already been made in this discussion.
 Also previously suggested is that you change to a bank that does not
discriminate against SeaMonkey.

-- 
David E. Ross

Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[J. Weaver Jr.]

Marisa Ciceran wrote:

I have been a faithful user of Seamonkey and its predecessors since the
mid-1990s. Have there been no updates to Seamonkey since the release of
version 2.40 in March 2016?

It is for months that I have been unable to log into my Chase bank
accounts because chase.com claims that Seamonkey is out of date.  I know
that there have been extensive discussions on this chronic problem, but
since I am not a programmer I have not been able to decipher from the
various threads whether or not a viable solution has been found. The
suggestions to change banks or stop using Seamonkey are not reasonable
options to me.

Can anyone please give this and other non-techie users a clue on the
status of this issue? I would appreciate it.


In a browser page address bar, type "about:config" (without the quotes).

Anywhere in the body of the page, right click, select "New" and "String".

At the "Enter the preference name" prompt, type 
"general.useragent.override.chase.com" (without the quotes).


At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0) 
Gecko/20100101 Firefox/43.0" (again, without the quotes).


Many other user agent strings will also work, but that one's working for 
me.  -JW

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

Re: Chase Bank doesn't like SeaMonkey

[Marisa Ciceran]

I have been a faithful user of Seamonkey and its predecessors since the 
mid-1990s. Have there been no updates to Seamonkey since the release of 
version 2.40 in March 2016?


It is for months that I have been unable to log into my Chase bank 
accounts because chase.com claims that Seamonkey is out of date.  I know 
that there have been extensive discussions on this chronic problem, but 
since I am not a programmer I have not been able to decipher from the 
various threads whether or not a viable solution has been found. The 
suggestions to change banks or stop using Seamonkey are not reasonable 
options to me.


Can anyone please give this and other non-techie users a clue on the 
status of this issue? I would appreciate it.


Thank you.

Marisa

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