Over the weekend the Chase website stopped working again. Looking in
the error console I see:

Error: Reference error: define is not defined

This is with UA for FireFox 102 ESR.

Any chance this will be fixed?

Using FireFox for the moment with Chase.

Dave

David H Durgee <dhdurgee@privacy.net> wrote:
> Over the weekend the Chase website stopped working again. Looking in
> the error console I see:

> Error: Reference error: define is not defined

> This is with UA for FireFox 102 ESR.

> Any chance this will be fixed?

> Using FireFox for the moment with Chase.

It and a few other web sites had always been broken for a long time. I
had to use Firefox. :(

--
"But let justice roll on like a river, righteousness like a never-failing stream!" --Amos 5:24. Y did winter come back & will summer B coming this weekend so soon? Tiry poopy taxy day. :(
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

On 4/19/2023 7:59 AM, David H Durgee wrote:
> Over the weekend the Chase website stopped working again.  Looking in
> the error console I see:
>
> Error: Reference error: define is not defined
>
> This is with UA for FireFox 102 ESR.
>
> Any chance this will be fixed?
>
> Using FireFox for the moment with Chase.
>
> Dave

Chase.com works for me with:
general.useragent.override.chase.com
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101
Firefox/105.0

Lemuel Johnson

Lemuel Johnson wrote:
> On 4/19/2023 7:59 AM, David H Durgee wrote:
>> Over the weekend the Chase website stopped working again.  Looking in
>> the error console I see:
>>
>> Error: Reference error: define is not defined
>>
>> This is with UA for FireFox 102 ESR.
>>
>> Any chance this will be fixed?
>>
>> Using FireFox for the moment with Chase.
>>
>> Dave
>
> Chase.com works for me with:
> general.useragent.override.chase.com
> Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101
> Firefox/105.0
>
> Lemuel Johnson
>

You are able to logon and access your accounts?

Dave

On 4/19/2023 11:15 AM, David H Durgee wrote:
> Lemuel Johnson wrote:
>> On 4/19/2023 7:59 AM, David H Durgee wrote:
>>> Over the weekend the Chase website stopped working again.  Looking in
>>> the error console I see:
>>>
>>> Error: Reference error: define is not defined
>>>
>>> This is with UA for FireFox 102 ESR.
>>>
>>> Any chance this will be fixed?
>>>
>>> Using FireFox for the moment with Chase.
>>>
>>> Dave
>>
>> Chase.com works for me with:
>> general.useragent.override.chase.com
>> Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101
>> Firefox/105.0
>>
>> Lemuel Johnson
>>
>
> You are able to logon and access your accounts?
>
> Dave

Yesterday yes, today no. Even with Firefox spoofed at 112.0. Lots of
IndexedDB errors.

lj

David H Durgee wrote:
> Over the weekend the Chase website stopped working again.  Looking in
> the error console I see:
>
> Error: Reference error: define is not defined

Does this error happen before having to log in, or only after?

If it happens before, what is the exact url that you enter into Seamonkey?

gerry 666uk wrote:
> David H Durgee wrote:
>> Over the weekend the Chase website stopped working again.  Looking in
>> the error console I see:
>>
>> Error: Reference error: define is not defined
>
> Does this error happen before having to log in, or only after?
>
> If it happens before, what is the exact url that you enter into Seamonkey?

It happens before. URL is:

https://secure07b.chase.com/#/dashboard/overviewAccounts/overview/index

Dave

David H Durgee wrote:
> It happens before.  URL is:
>
> https://secure07b.chase.com/#/dashboard/overviewAccounts/overview/index

The problem with setting the UA string to Firefox 102 is that it won't
make sense unless the browser really does implement all the features of
Firefox 102. Scripts will assume features exist that probably don't
exist in Seamonkey.

Before it gets to the error about the Reference Error, it hits a number
of different errors, e.g.

SyntaxError: missing : after property id 433.1985834d963ed8cc2b4a.js:1:2153

it's probably best to start with the first error, and then work from there.

It could be that the reason "define is not defined" is because of an
earlier error, preventing it getting that far.

gerry 666uk wrote:
> David H Durgee wrote:
>> It happens before.  URL is:
>>
>> https://secure07b.chase.com/#/dashboard/overviewAccounts/overview/index
>
> The problem with setting the UA string to Firefox 102 is that it won't
> make sense unless the browser really does implement all the features of
> Firefox 102. Scripts will assume features exist that probably don't
> exist in Seamonkey.
>
> Before it gets to the error about the Reference Error, it hits a number
> of different errors, e.g.
>
> SyntaxError: missing : after property id 433.1985834d963ed8cc2b4a.js:1:2153
>
> it's probably best to start with the first error, and then work from there.
>
> It could be that the reason "define is not defined" is because of an
> earlier error, preventing it getting that far.

I had it set to FireFox 78 until they started issuing warnings that they
were removing support for that release. Checking at their page
documenting minimums showed that they require FireFox 98.0 or higher.
Seeing that 102 was the ESR release I thought that a better choice.

This worked until the past weekend. So it appears they made some sort
of script change very recently that broke things.

If you have an easy way to test with a FireFox 98.0 UA I would be
interested to know if it works, as in that case I will change my UA to
that release. If it is still broken, then I will have to wait until
whatever crud they have added is supported in a future SeaMonkey release.

Dave

On 4/20/2023 2:25 PM, David H Durgee wrote:
> gerry 666uk wrote:
>> David H Durgee wrote:
>>> It happens before.  URL is:
>>>
>>> https://secure07b.chase.com/#/dashboard/overviewAccounts/overview/index
>>
>> The problem with setting the UA string to Firefox 102 is that it won't
>> make sense unless the browser really does implement all the features
>> of Firefox 102. Scripts will assume features exist that probably don't
>> exist in Seamonkey.
>>
>> Before it gets to the error about the Reference Error, it hits a
>> number of different errors, e.g.
>>
>>
>> it's probably best to start with the first error, and then work from
>> there.
>>
>> It could be that the reason "define is not defined" is because of an
>> earlier error, preventing it getting that far.
>
> I had it set to FireFox 78 until they started issuing warnings that they
> were removing support for that release.  Checking at their page
> documenting minimums showed that they require FireFox 98.0 or higher.
> Seeing that 102 was the ESR release I thought that a better choice.
>
> This worked until the past weekend.  So it appears they made some sort
> of script change very recently that broke things.
>
> If you have an easy way to test with a FireFox 98.0 UA I would be
> interested to know if it works, as in that case I will change my UA to
> that release.  If it is still broken, then I will have to wait until
> whatever crud they have added is supported in a future SeaMonkey release.
>
> Dave

FF 98 doesn't work either.

lj

Lemuel Johnson wrote:
> On 4/20/2023 2:25 PM, David H Durgee wrote:
>> gerry 666uk wrote:
>>> David H Durgee wrote:
>>>> It happens before.  URL is:
>>>>
>>>> https://secure07b.chase.com/#/dashboard/overviewAccounts/overview/index
>>>
>>> The problem with setting the UA string to Firefox 102 is that it
>>> won't make sense unless the browser really does implement all the
>>> features of Firefox 102. Scripts will assume features exist that
>>> probably don't exist in Seamonkey.
>>>
>>> Before it gets to the error about the Reference Error, it hits a
>>> number of different errors, e.g.
>>>
>>>
>>> it's probably best to start with the first error, and then work from
>>> there.
>>>
>>> It could be that the reason "define is not defined" is because of an
>>> earlier error, preventing it getting that far.
>>
>> I had it set to FireFox 78 until they started issuing warnings that
>> they were removing support for that release.  Checking at their page
>> documenting minimums showed that they require FireFox 98.0 or higher.
>> Seeing that 102 was the ESR release I thought that a better choice.
>>
>> This worked until the past weekend.  So it appears they made some sort
>> of script change very recently that broke things.
>>
>> If you have an easy way to test with a FireFox 98.0 UA I would be
>> interested to know if it works, as in that case I will change my UA to
>> that release.  If it is still broken, then I will have to wait until
>> whatever crud they have added is supported in a future SeaMonkey release.
>>
>> Dave
>
> FF 98 doesn't work either.
>
> lj

I'm not surprised. Perhaps someone with the expertise can figure out
what they have changed that must now be added to SeaMonkey in order for
the website to work again. Then frg can add it to the list with
whatever priority is appropriate.

Dave

On 19/04/2023 13:59, David H Durgee wrote:
> Over the weekend the Chase website stopped working again.� Looking in
> the error console I see:
>

Did you mean to say that SeaMonkey is broken again rather than Chase
Website broken.

I find it very difficult to accept that a bank's website is broken
because they are running a multi-billion dollar business and website is
their main asset these days considering branches are closing down and
people are resorting to web based services.

SM is broken a very long time ago and the people currently using it for
any serious work on it are just a handful here on these newsgroups. You
need to use Firefox or Google Chrome because these are upgraded quite
regularly to meet any challenges people face when dealing with financial
and personal matters online.

Arlene S. Peters wrote:
> On 19/04/2023 13:59, David H Durgee wrote:
>> Over the weekend the Chase website stopped working again.  Looking in
>> the error console I see:
>>
>
> Did you mean to say that SeaMonkey is broken again rather than Chase
> Website broken.
>
> I find it very difficult to accept that a bank's website is broken
> because they are running a multi-billion dollar business and website is
> their main asset these days considering branches are closing down and
> people are resorting to web based services.
>
> SM is broken a very long time ago and the people currently using it for
> any serious work on it are just a handful here on these newsgroups. You
> need to use Firefox or Google Chrome because these are upgraded quite
> regularly to meet any challenges people face when dealing with financial
> and personal matters online.
>

Even a narrow minded individual like you should know better. These websites
are usually just cobbled together using the latest free stuff available. What
matters ins only the corporate design not the functionality. There is no money
made enhancing a website for online or transaction banking using costly tools.
That means bleeding edge not something customers need or want. They don't care
about browser upgrades they only care about low support costs which means just
use Chrome because the people cobbling together the free stuff are the same
clueless ones pushing arbitrary web standards these days to be hip. And google
is happy to expanding its monopoly and pushing out more arbitrary stuff and
standards to protect its ad business. So everyone on the google train wins and
can do press releases how they do modern web development.

For desktop users in general most banking websites are now a joke. And a sure
bet support for Firefox is being phased out next.

FRG

frg wrote:
> Arlene S. Peters wrote:
>> On 19/04/2023 13:59, David H Durgee wrote:
>>> Over the weekend the Chase website stopped working again.  Looking in
>>> the error console I see:
>>>
>>
>> Did you mean to say that SeaMonkey is broken again rather than Chase
>> Website broken.
>>
>> I find it very difficult to accept that a bank's website is broken
>> because they are running a multi-billion dollar business and website is
>> their main asset these days considering branches are closing down and
>> people are resorting to web based services.
>>
>> SM is broken a very long time ago and the people currently using it for
>> any serious work on it are just a handful here on these newsgroups. You
>> need to use Firefox or Google Chrome because these are upgraded quite
>> regularly to meet any challenges people face when dealing with financial
>> and personal matters online.
>>
>
> Even a narrow minded individual like you should know better. These
> websites are usually just cobbled together using the latest free stuff
> available. What matters ins only the corporate design not the
> functionality. There is no money made enhancing a website for online or
> transaction banking using costly tools. That means bleeding edge not
> something customers need or want. They don't care about browser upgrades
> they only care about low support costs which means just use Chrome
> because the people cobbling together the free stuff are the same
> clueless ones pushing arbitrary web standards these days to be hip. And
> google is happy to expanding its monopoly and pushing out more arbitrary
> stuff and standards to protect its ad business. So everyone on the
> google train wins and can do press releases how they do modern web
> development.
>
> For desktop users in general most banking websites are now a joke. And a
> sure bet support for Firefox is being phased out next.
>
> FRG

Thank you for responding in this thread. If they were to properly
design websites to detect the features they require and those they can
take advantage of if available as opposed to simply sniffing the UA we
would have many more websites that would work with most browsers.

I hope you will have time to research what they are looking for now that
SeaMonkey is not currently supporting to allow me to resume using it
with their website with a FireFox UA since they insist on one. This is
one of only two websites that I need that I must use another browser for.

Thank you for your continued support of SeaMonkey. You deserve all the
support we users can give.

Dave