Parts of AMX Card website fails to work in beta2

[Pallid Planetoid]

The American Express Card website fails to work in Pale Moon beta2 when a "Redeem for Cash" is requested on the website.

I recognize that a log-in is required to test this so all I can do is provide the error information when attempting to make this transaction on the website as illustrated below.

FWIW -- This "Redeem for Cash" function also fails in the same manner using Basilisk.

Both Pale Moon 28.0.0b2 (in Safe Mode) and Basilisk (FWIW) get to this point and stop:

what I get in AMX when redeeming cash back.png

The "Redeem for Cash" function DOES WORK like a charm using the Internet Explorer 11 Browser.

Browser Console:

ReferenceError: event is not defined[Learn More]

Error Console:

Error:
Timestamp: 7/5/2018 1:36:41 AM
Error: ReferenceError: event is not defined
Source File: https://rewarddollars.americanexpress.c ... EqW3FkdYE1
Line: 1
Warning:
Timestamp: 7/5/2018 1:36:42 AM
Warning: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://rewards.americanexpress.com/myc ... 731&p2=eps. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
Warning:
Timestamp: 7/5/2018 1:37:39 AM
Warning: ReferenceError: reference to undefined property "_originalListener"
Source File: resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/event-emitter.js
Line: 162
Warning:
Timestamp: 7/5/2018 1:37:39 AM
Warning: ReferenceError: reference to undefined property "attachEventsTimer"
Source File: resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/widgets/tooltip/HTMLTooltip.js
Line: 447

Now that I was able to successfully perform the procedure on the Internet Explorer 11 browser I will not be able to do any testing again until redeemable cash is accumulated once again.

[Moonchild]

You should report this to AMX. The errors shown are all server-side issues or unknowns.

[Pallid Planetoid]

You should report this to AMX. The errors shown are all server-side issues or unknowns.

I'll be more than happy to take the time to do this and will be sure to report back their feedback. That said, FWIW --- AMX says as reported on their website regarding their on-line "accessibility" is that they attempt to quote: "conform the accessibility of our websites to the Web Content Accessibility Guidelines (v 2.0) as recommended by the World Wide Web Consortium (W3C)".

While I fully agree with you on where the responsibility lies regarding this issue on their website and will make the case to them on this very point.

That said, I have a Question --- what do I say if after testing this function on a few browsers their support staff follow up by saying the "Redeem for Cash" procedure does actually work on browsers such as: Chrome, Firefox, IE11 etc.? (I only ask this because of the fact I was able to successfully perform the function using IE11. Which then as I am sure you would agree begs the question would the procedure have also worked on Chrome, Firefox etc. if I had tried it on these browsers instead of IE11 like I did?)

I am fully aware that I can insist that their website errors "are all server-side issue or unknowns" and as such are their responsibility (which btw, I WILL gladly DO!) -- but it seems to me and possibly you might agree as well the point I would be attempting to get across to their support team may potentially ring hollow if in fact a number of relatively popular browsers are able to perform the function regardless.

[GMforker]

AFAIK - throws "ReferenceError: event is not defined" because it use window.event - and it isn't a standard. But see also: bug #218415 (Request for window.event object added to DOM to ease cross browser scripting)

[Moonchild]

Issue opened for web compat: Issue #595 (UXP)