chase.com bank login will not load page in Pale Moon Topic is solved

For support with specific websites

Moderator: trava90

Forum rules
Please always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.

Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
  1. Clear any current output
  2. Navigate or refresh the page in question
  3. Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
User avatar
TechnoMage
Moongazer
Moongazer
Posts: 13
Joined: 2022-03-21, 04:51

Re: chase.com bank login will not load page in Pale Moon

Unread post by TechnoMage » 2023-05-01, 01:02

pshipwrite wrote:
2023-04-18, 21:47
Thanks much, adoxa, for a solution to the Chase Bank login problem! The Modify HTTP Response extension, with the filter code added, works fine. Thanks again!!
DITTO!

User avatar
__NM64__
Lunatic
Lunatic
Posts: 359
Joined: 2013-10-17, 05:29
Location: Northeast Ohio

Re: chase.com bank login will not load page in Pale Moon

Unread post by __NM64__ » 2023-05-29, 03:13

By the way, Chase "just works" on Pale Moon 32.2.0.

...kind of. Within a week after Pale Moon 32.2.0 was released, Chase seemed to either update and/or incorporate user-agent sniffing and now Pale Moon's default "Firefox compatibility" user agent doesn't work with it: When trying to access the above link, you'll see the following "use a compatible browser" screen with Pale Moon's default user agent(s): Manually applying a user agent that was copy-and-pasted from the newest Firefox (v113 as of this post) made Chase no longer complain about Pale Moon being incompatible. From farther testing, even using the same version that Pale Moon reports (v102.0) has Chase work without issue:

Code: Select all

Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0
After a bunch of trial and error, the only conclusion I can come to is that Chase is not only sniffing to check if your browser is a new enough version of a known-compatible browser (e.g. a user agent with Firefox v79.0 doesn't work but a user again with Firefox v89.0 does), but they're even straight-up detecting if "PaleMoon/[insert version here]" is in the user agent and, if so, automatically treating your browser as incompatible.

I say this because renaming the "PaleMoon" part of the user agent to instead say "PaleMoo32.2.0" made Chase work, but making it say "PaleMoo/32.2.0" did not. Similarly, removing the version number altogether and just saying "PaleMoon" didn't work and neither did increasing PaleMoon's version number.


In other words, the following user agents did not work:

Code: Select all

Mozilla/5.0 (X11; Linux x86_64; rv:6.2) Goanna/20230516 PaleMoon/32.2.0
Mozilla/5.0 (X11; Linux x86_64; rv:6.2) Goanna/20230516 PaleMoo32.2.0
Mozilla/5.0 (X11; Linux x86_64; rv:6.2) Goanna/20230516 PaleMoo
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 PaleMoon/32.2.0
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 PaleMoon32.2.0
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 PaleMoo
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 Firefox/102.0 PaleMoon/32.2.0
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 Firefox/102.0 PaleMoon/32.2
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 Firefox/102.0 PaleMoon/92.2
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 Firefox/102.0 PaleMoo/32.2.0
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 Firefox/102.0 PaleMoon
Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0
...while the following user agents did work:

Code: Select all

Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Goanna/6.2 Firefox/102.0 PaleMoo32.2.0
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Goanna/6.2 Firefox/102.0 PaleMoo
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 Firefox/102.0 PaleMoo32.2.0
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Goanna/6.2 Firefox/102.0 PaleMoo
Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0
Mozilla/5.0 (X11; Linux x86_64; rv:999.0) Gecko/20100101 Firefox/999.0

User avatar
Pallid Planetoid
Knows the dark side
Knows the dark side
Posts: 4279
Joined: 2015-10-06, 16:59
Location: Los Angeles CA USA

Re: chase.com bank login will not load page in Pale Moon

Unread post by Pallid Planetoid » 2023-05-29, 03:44

I'm having no issues (in Windows) as result of doing the following:
1) Using the "Modify HTTP Response" filter posted HERE by adoxa in this topics previous page
2) and using the general.useragent.override.chase.com value of "Mozilla/5.0 (%OS_SLICE% rv:112.0) Gecko/20100101 Firefox/112.0".
Current Pale Moon(x86) Release | WIN10 | I5 CPU, 1.7 GHz, 6GB RAM, 500GB HD[20GB SSD]
Formerly user Pale Moon Rising - to provide context involving embedded reply threads.
Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

User avatar
__NM64__
Lunatic
Lunatic
Posts: 359
Joined: 2013-10-17, 05:29
Location: Northeast Ohio

Re: chase.com bank login will not load page in Pale Moon

Unread post by __NM64__ » 2023-05-29, 05:06

Pallid Planetoid wrote:
2023-05-29, 03:44
I'm having no issues (in Windows) as result of doing the following:
1) Using the "Modify HTTP Response" filter posted HERE by adoxa in this topics previous page
2) and using the general.useragent.override.chase.com value of "Mozilla/5.0 (%OS_SLICE% rv:112.0) Gecko/20100101 Firefox/112.0".
Why wouldn't you just use Pale Moon's built-in about:config setting for per-website user agent overrides? I personally like to use my various custom about:config settings via a mozilla.cfg file to make things easier to keep track of so, for chase.com, it'd simply the following:

Code: Select all

lockPref("general.useragent.override.chase.com", "Mozilla/5.0 (X11; Linux x86_64; rv:112.0) Gecko/20100101 Firefox/112.0");

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35474
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: chase.com bank login will not load page in Pale Moon

Unread post by Moonchild » 2023-05-29, 13:29

OK, updating the default override for chase.com...
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
Pallid Planetoid
Knows the dark side
Knows the dark side
Posts: 4279
Joined: 2015-10-06, 16:59
Location: Los Angeles CA USA

Re: chase.com bank login will not load page in Pale Moon

Unread post by Pallid Planetoid » 2023-07-12, 15:35

Updated to PMv32.3 yesterday - trying to login to Chase bank for the first time since the update consistently fails.

Note: that the Chase bank website works fine w/out any issues in other browsers.

However, the Chase bank website is very unstable in Pale Moon since the new update. Testing in Safe-Mode the login page usually does not work, for the most part it does one of two things:'
1) blue page with spinning circle
2) when I do occasionally get a login page the page is usually unresponsive - I can enter UID/PWD but that's it no response to any attempts to login.

The few exceptions are I can occasionally get past the login interface but the process to send a code to verify me (probably because I'm in Safe-Mode) persistently fails to work - I can get the code and enter it but it doesn't work. I get the call back from bank saying that the I've been confirmed - but that's it.

Obtaining the error codes were very difficult.

They will display for awhile and then disappear from the error console -- in other words two errors eventually display while the login is attempting to work but after a short time (minute or so) the errors get cleared from the console.

Eventually, I managed to capture the two error codes however so here they are (hope it helps):

Code: Select all

Timestamp: 7/12/2023 8:04:50 AM
Error: ReferenceError: define is not defined
Source File: https://static.chasecdn.com/web/library/@seur/cxo-ui-common-utilities/12.22.9/common/js/kit/main.js
Line: 1
Timestamp: 7/12/2023 8:13:33 AM
Error: ReferenceError: define is not defined
Source File: https://static.chasecdn.com/web/hash/appkit/js/main_b646aea3f7a590b8776f4b396e81e784.js
Line: 1
One time when the errors above cleared from the error console I momentarily got this error (that I was fortunately able to capture eventually):

Code: Select all

[object XULElement]
Login Screen-shots:
Get this most of the time
Get this most of the time
If I'm able to get a login it will usually not work but if it does the website fails to successfully complete a login.
after a few attempts - I was able to capture the errors and posted them above
after a few attempts - I was able to capture the errors and posted them above
Current Pale Moon(x86) Release | WIN10 | I5 CPU, 1.7 GHz, 6GB RAM, 500GB HD[20GB SSD]
Formerly user Pale Moon Rising - to provide context involving embedded reply threads.
Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

User avatar
Pallid Planetoid
Knows the dark side
Knows the dark side
Posts: 4279
Joined: 2015-10-06, 16:59
Location: Los Angeles CA USA

Re: chase.com bank login will not load page in Pale Moon

Unread post by Pallid Planetoid » 2023-07-12, 16:54

I've noted that It appears the two error codes are similar (if not the same) in regards to the errors posted at the beginning of this topic.

However, at this point the issue appears to be resolved in my case (see below).

As to the UA Override setting (that has been discussed in this topic) I've been using FWIW (as before) "Mozilla/5.0 (%OS_SLICE% rv:112.0) Gecko/20100101 Firefox/112.0".

Changing it to another value as suggested in this topic "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0" appears to fix the issues with Chase that I've had today.

Just to confirm - when I switched back to the value I was using before "Mozilla/5.0 (%OS_SLICE% rv:112.0) Gecko/20100101 Firefox/112.0" the browser locked up forcing me to abort (stop the PM process) the browser. As I recall, I was able to login this time - but right away, using a fundamental part of the website caused the browser to lockup (not responding).

Once again changing back to the UA Override value to "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0" produces good results in that I am able to login and successfully use the website.

Why the differences in results between the two UA Override values is an interesting question.....

So I guess at this point - my posted issues can be considered resolved by using the UA Override referenced above. :thumbup:
Current Pale Moon(x86) Release | WIN10 | I5 CPU, 1.7 GHz, 6GB RAM, 500GB HD[20GB SSD]
Formerly user Pale Moon Rising - to provide context involving embedded reply threads.
Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35474
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: chase.com bank login will not load page in Pale Moon

Unread post by Moonchild » 2023-07-12, 20:10

so we're forever chasing chase eh?
I'll remove the specific override again then.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
__NM64__
Lunatic
Lunatic
Posts: 359
Joined: 2013-10-17, 05:29
Location: Northeast Ohio

Re: chase.com bank login will not load page in Pale Moon

Unread post by __NM64__ » 2023-07-12, 20:14

Moonchild wrote:
2023-07-12, 20:10
so we're forever chasing chase eh?
I'm not sure that's correct—the previous reply states that the issue seems to be how the useragent override specifies Firefox 112, but using 102 instead makes it work.

If we were "forever chasing chase" then I would think it'd be the opposite, i.e. if 102 was the current and it didn't work with it, but worked with 112.

(and yes, I'm aware of the pun)

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35474
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: chase.com bank login will not load page in Pale Moon

Unread post by Moonchild » 2023-07-12, 20:24

No, it broke plenty of times before
Previously, only 112 worked (see earlier in thread) so I instated that as a default override in the pale moon config.
now, we're back to only 102 working (the default version for overrides)... :crazy:

it's just a prayer without end. I'm tired of Chase bank constantly breaking shit somehow for us (in articular, me, since I'm the one making these SSOAU updates) to jump through hoops for backwards useragent sniffing.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
__NM64__
Lunatic
Lunatic
Posts: 359
Joined: 2013-10-17, 05:29
Location: Northeast Ohio

Re: chase.com bank login will not load page in Pale Moon

Unread post by __NM64__ » 2023-07-12, 20:35

Moonchild wrote:
2023-07-12, 20:24
it's just a prayer without end. I'm tired of Chase bank constantly breaking shit somehow for us (in articular, me, since I'm the one making these SSOAU updates) to jump through hoops for backwards useragent sniffing.
Well, I just re-verified that, when logging in from https://secure.chase.com on Pale Moon 32.2.1, everything... just works.

Sooooo...

(32.3.0 hasn't been pushed yet for Steve Pusser's Ubuntu PPA, so I can't properly test that version yet since Chase is something that gets picky about wanting verification if logging in from what it thinks is a "different device" which includes using a separate browser installation or the like)


EDIT: And I can at least confirm that I can access https://secure.chase.com with the tarball of PM 32.3.0 without any problem, but I didn't try logging in due to the aforementioned issue where Chase will think it's a different device (which, in this specific instance, is actually the case since I tested that tarball via the Linux Mint live ISO)

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35474
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: chase.com bank login will not load page in Pale Moon

Unread post by Moonchild » 2023-07-13, 06:01

__NM64__ wrote:
2023-07-12, 20:35
Sooooo...
Sooooo what?

I undid the override also in dynamic UA updates sooooo you may be sending a working UA after my previous post.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
__NM64__
Lunatic
Lunatic
Posts: 359
Joined: 2013-10-17, 05:29
Location: Northeast Ohio

Re: chase.com bank login will not load page in Pale Moon

Unread post by __NM64__ » 2023-07-13, 06:07

Moonchild wrote:
2023-07-13, 06:01
I undid the override also in dynamic UA updates sooooo you may be sending a working UA after my previous post.
Wait, are you saying that those can be updated completely separately from the browser? So even though I'm still on 32.2.1, I would still receive an updated user agent override?

...I had no idea Pale Moon contained such a function. My previous post was purely under the impression that Pale Moon 32.2.1 tested today would be the exact same Pale Moon configuration as from, say, a week ago.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35474
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: chase.com bank login will not load page in Pale Moon

Unread post by Moonchild » 2023-07-13, 07:52

It's something that flies mostly under the radar but it was discussed before.
Pale Moon includes a feature where it will check for a json file on the dynamic UA updates server, and that will override browser-supplied defaults (but not user-set defaults). It was introduced to enable "emergency overrides" that would take effect immediately without a new browser version being needed. Primarily for things like frameworks of top-10 websites breaking and needing an override.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
Pallid Planetoid
Knows the dark side
Knows the dark side
Posts: 4279
Joined: 2015-10-06, 16:59
Location: Los Angeles CA USA

Re: chase.com bank login will not load page in Pale Moon

Unread post by Pallid Planetoid » 2023-07-13, 17:22

__NM64__ wrote:
2023-07-12, 20:14
Moonchild wrote:
2023-07-12, 20:10
so we're forever chasing chase eh?
I'm not sure that's correct—the previous reply states that the issue seems to be how the useragent override specifies Firefox 112, but using 102 instead makes it work.

If we were "forever chasing chase" then I would think it'd be the opposite, i.e. if 102 was the current and it didn't work with it, but worked with 112.

(and yes, I'm aware of the pun)
I'm not sure if this is getting overlooked and in fact is meaningful anyway -- but the differences between the UAO that works and doesn't work includes more than just version number - there is also the reference to "Linux" to consider.

What was working (I've been using and was presumably the "default") and stopped working in my case is: Mozilla/5.0 (%OS_SLICE% rv:112.0) Gecko/20100101 Firefox/112.0 (has no reference to "Linux").

What I changed to (based on posted suggestion in this topic) that works is the following:
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 (I was aware that this setting above had been previously working at the same time the one I went with [absent the "Linux" reference] that was also at the time working)

I have no idea if "112" would actually work (or was relevant in any way) in combination with the "Linux" reference or not - I simply used the suggested UAO posted in this topic (that happened to use version "102") and when I found that was still working (as before) I reported this as a working UAO....

So I'm thinking that the version "112" is likely not the critical factor so whether it's "102" or "112" may not be a factor but rather the reference to "Linux" is likely the more critical factor....

Based on my assumption above, I'll try a the following examples w/ "Linux" reference (keeping in mind we know this works that I reported as working "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0":
I first tested for Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 (that I had found worked) - and I'm sorry to report the login worked but attempting a fundamental function of the website (opening the checking account records locked the browser which I had to abort [stop process via Windows T.M.} fortunately restarting Pale Moon persevered the former tabs and I was able to return to this in progress post)
So getting back to testing.... Btw, not only was this post (in progress) tab preserved - but the Chase account was still logged-in when I restarted Pale Moon (after aborting the previous Pale Moon process that was locked up).
So to continue with my intended testing...

The UAO "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0" worked this time as I was able to use the website (fundamental function that previously locked-up Pale Moon worked fine. Now to test the next to UAO's.... (this is getting more complicated than I had intended.... :crazy:)

So continuing to test the following:
Mozilla/5.0 (X11; Linux x86_64; rv:112.0) Gecko/20100101 Firefox/112.0
Mozilla/5.0 (X11; Linux x86_64; rv:115.0) Gecko/20100101 Firefox/115.0

Both of the above worked fine


As a "sanity check" (since the 1st time PM locked-up testing functions of the website) I returned to the UAO (that formerly locked-up PM on the first test): Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0

And it worked just fine this time - so I can't explain the unfortunate (outlier) PM lockup experience.... :crazy: (apparently a random outlier issue perhaps)

As an additional "sanity check" I tested the former Mozilla/5.0 (%OS_SLICE% rv:112.0) Gecko/20100101 Firefox/112.0 - that has no reference to "Linux" that was not working that led to my post about what I had found yesterday (made a copy of this post-in-progress in case of problems testing this)

The UAO (above) test failed (w/out the reference to "Linux" - what occurred was I entered my UID/PWD but it did not work both inputs disappear and I end up with the login page w/out any entries (which is what I had been getting before some of the time using this UAO w/out the reference to "Linux".

I don't want to take this any further (re: testing) - my conclusion is the following:
1) the UAO that does not reference "Linux": Mozilla/5.0 (%OS_SLICE% rv:112.0) Gecko/20100101 Firefox/112.0 fails to work properly
1a) I'm going to assume this same result would be the case regardless of what version is entered (i.e the reference to "Linux" is the critical factor in regards to "success")
2) the UAO that DOES reference "Linux": Mozilla/5.0 (X11; Linux x86_64; rv:112.0) Gecko/20100101 Firefox/112.0 works regardless of the version number as tested above.

So my conclusion: Version is irrelevant as apposed to the reference to "Linux" that is what's relevant.

So... it's not a matter of "chasing" incremental version numbers as much as it is the reference to "Linux" is what is relevant

Overall conclusion: we are NOT really "chasing" version number increments as much (perhaps this may be a factor at some point) as the critical part of all of this is using the reference to "Linux" considering the fact various version numbers all worked when using the "Linux" reference based on my results ;)
Current Pale Moon(x86) Release | WIN10 | I5 CPU, 1.7 GHz, 6GB RAM, 500GB HD[20GB SSD]
Formerly user Pale Moon Rising - to provide context involving embedded reply threads.
Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35474
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: chase.com bank login will not load page in Pale Moon

Unread post by Moonchild » 2023-07-13, 18:52

Pallid Planetoid wrote:
2023-07-13, 17:22
version "112" is likely not the critical factor so whether it's "102" or "112" may not be a factor but rather the reference to "Linux" is likely the more critical factor...
i'm sorry but if that's the case then chase's website is in an even worse state than I initially thought. in what universe would a mainstream browser with the same version number but on a different platform have a different feature set (since that is what they are "detecting" by checking versions...). Not this one, for sure.
So no, that makes no sense whatsoever.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
Pallid Planetoid
Knows the dark side
Knows the dark side
Posts: 4279
Joined: 2015-10-06, 16:59
Location: Los Angeles CA USA

Re: chase.com bank login will not load page in Pale Moon

Unread post by Pallid Planetoid » 2023-07-13, 22:35

Moonchild wrote:
2023-07-13, 18:52
Pallid Planetoid wrote:
2023-07-13, 17:22
version "112" is likely not the critical factor so whether it's "102" or "112" may not be a factor but rather the reference to "Linux" is likely the more critical factor...
i'm sorry but if that's the case then chase's website is in an even worse state than I initially thought. in what universe would a mainstream browser with the same version number but on a different platform have a different feature set (since that is what they are "detecting" by checking versions...). Not this one, for sure.
So no, that makes no sense whatsoever.
Note: My edit to the terms referenced (above) in red.

What my test results have demonstrated (to the extent of what I've tested) is that "versions" were irrelevant as far as what works as opposed to the "Linux" reference that did make a difference as far as what works.

To clarify, my results show absent the "Linux" reference it makes no difference re: versions the UAO will FAIL TO WORK in any case, however with the "Linux" reference included in the UAO then the UAO WILL WORK and it will work using various version numbers. Wouldn't that lead us to the conclusion that the critical "success factor" of the UAO setting is the inclusion of "Linux" (regardless if it makes any sense or not...)?

Breakdown (to further clarify) in regards to what my results appear to demonstrate (to the extent of what I included in my tests):
1) UAO setting w/out the reference to "Linux" (regardless of version) failed in my case (for all tests).
2) UAO settings w/ the reference to "Linux" (regardless of version I tested for) was successful in all cases.
Conclusion: As long as "Linux" is included in the UAO then the UAO consistently worked (regardless of versions I had tested for), as opposed to if the reference to "Linux" is not included in the UAO setting in which case the UAO did not work (regardless of version numbers).

Whether my results makes sense or not (I'm not speaking to this in as much as I'm admittedly not qualified) -- the "breakdown" referenced above was undeniably my results (FWIW) in regards to what in my case impacted whether or not the UAO worked. ;)
Current Pale Moon(x86) Release | WIN10 | I5 CPU, 1.7 GHz, 6GB RAM, 500GB HD[20GB SSD]
Formerly user Pale Moon Rising - to provide context involving embedded reply threads.
Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

User avatar
__NM64__
Lunatic
Lunatic
Posts: 359
Joined: 2013-10-17, 05:29
Location: Northeast Ohio

Re: chase.com bank login will not load page in Pale Moon

Unread post by __NM64__ » 2023-07-13, 22:57

Even though it's kind of a pain, I can actually do the authentication process for a "new device" or what-not...

So I could totally put together a video recording showing an incredibly reproducible environment going through and testing some of these things, proving once and for all just what works and what doesn't.

Locked