EDIT
I tried changing the UA override to:
Code: Select all
Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0 (Pale Moon)
Moderator: trava90
Code: Select all
Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0 (Pale Moon)
Code: Select all
Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
Make sure to contact the bank...pshipwrite wrote: ↑2019-12-27, 18:40I hope this issue can be resolved since PM is my primary browser.
Citibank isn't going to care about supporting Pale Moon -- they are just going to say that PM isn't an acceptable browser and that will be the end of it.back2themoon wrote: ↑2019-12-27, 20:22Make sure to contact the bank...pshipwrite wrote: ↑2019-12-27, 18:40I hope this issue can be resolved since PM is my primary browser.
First of all -- point of reference; this recent issue also occurs in Windows (in my case Win10).pshipwrite wrote: ↑2019-12-27, 20:38I agree with you, back2themoon, I would switch to another bank if I could. However, given the unique financial relationship I have with Citi, that is not possible at this time.
No need --- Refer to this post regarding same topic involving Windows viewtopic.php?f=3&t=23513&p=180719#p180719 that answers this question (same issue present in the prior Pale Moon release).Pallid Planetoid wrote: ↑2019-12-30, 02:11.... I'm also wondering if the PM 28.8 update may be contributing to the problem instead of any Citibank modifications to their web-page.
This issue has started very close in proximity of time to the PM 28.8 update when thinking back to when this all started. And the issue persists in Safe-Mode and using a new clean profile for what that's worth.....
So if anyone is still using the prior release of PM and are using Citibank -- please post your results using the bank -- thanks in advance.
For what it's worth this is what I get for errors in the Web Console:
Code: Select all
Timestamp: 12/30/2019 6:06:58 PM
Error: ReferenceError: mboxCreate is not defined
Source File: https://online.citi.com/US/JPS/portal/Index.do?Promo_ID=SPBL
Line: 948
Timestamp: 12/30/2019 6:07:02 PM
Error: TypeError: document.getElementById(...) is null
Source File: chrome://butwhymod/content/browser.js
Line: 28
Timestamp: 12/30/2019 6:07:46 PM
Error: TypeError: document.getElementById(...) is null
Source File: chrome://butwhymod/content/browser.js
Line: 28
Hmm, another perspective would be to approach the situation from the opposite direction --- that is to say (in full recognition that they are not the same browser just as most browsers are not the same in many respects); if the page works in a little known XUL browser like Basilisk then one could surmise there might be a way to make the same page work an another better known XUL browser like Pale Moon. (that is, from the perspective of a neophyte.... )