On 8/30/16, JAS <[email protected]> wrote:
> Ed Mullen wrote:
>> On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:
>>> J. Weaver Jr. wrote:
>>>> Mark B wrote:
>>>>> Chase Bank recently updated their websites, and now they won't allow
>>>>> access using SeaMonkey.  They say "You need to upgrade your browser to
>>>>> access your accounts and statements.  Download a new version of your
>>>>> favorite browser here:
>>>>>       Internet Explorer > (download the latest version.)
>>>>>       Firefox > (download the latest version)
>>>>>       Chrome > (download the lastest version)
>>>>>       Safari >"
>>>>>
>>>>> I have been using SM for years to access Chase.  Not about to use
>>>>> another browser just to do it their way.
>>>>>
>>>>> Call Chase Online services (877) 260-2178 and file a complaint.  The
>>>>> first person you talk to can't do anything, so ask to escalate the
>>>>> complaint.  I told them it was their problem, and gave them the user
>>>>> agent string: (Help/About SM) User agent: Mozilla/5.0 (Windows NT 6.1;
>>>>> WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40.
>>>>>
>>>>> If enough people complain, they might do something about it other than
>>>>> say "We don't support SM."  To which the reply should be "I don't
>>>>> support you."
>>>>
>>>> Solved that problem here by adding this preference to "about:config":
>>>>
>>>>      general.useragent.override.chase.com
>>>>
>>>> (type "string") with the following value:
>>>>
>>>>      Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0
>>>>
>>>> Yes, it'll have to be updated manually as SM advances, but WORKS4ME.
>>>> -JW
>>>
>>> Thanks for that.  It does work, but a PITA to remember every time SM
>>> updates.
>>
>> If you put it in a user.js file it will carry over to an update.
>>
>>
> It does not work for me using Windows XP and Seamonkey 2.40, any ideas??
> JAS

Assuming putting it in user.js is what isn't working for you, please
copy the line from your user.js & paste it into your reply.

If you also add
user_pref("00_user.js.loaded", "user.js load failed");
as the first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the last line then you can look at the results of "about:config"
and see if user.js was loaded completely (00_user.js.loaded = yes) or
if there was a problem loading it (in my case it's usually leaving off
the trailing ";" that breaks things)


If you're using firefox - right - it doesn't work. See
  https://bugzilla.mozilla.org/show_bug.cgi?id=896114
for why they disabled that functionality and
  https://bugzilla.mozilla.org/show_bug.cgi?id=933959
  general.useragent.override.[domain] (about:config entry) stopped working
  VERIFIED WONTFIX

Then take a look at
  http://www.netmarketshare.com/browser-market-share.aspx?qprid=1&qpcustomb=0
where firefox is now below 10% market share.  Duh.

Lee
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to