1265258 - Firefox for Android issue with processing payment on banking website (due to non-standard global event object usage)

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect, P1)

Description

[G-Sanchez10]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; InfoPath.3; McAfee; rv:11.0) like Gecko

Steps to reproduce:

1)Open Firefox for android Version 45.0.2
2)Go to Bank of America website and log in
3)On the Account Overview click on a credit card account.
4)On the Credit Card Overview, click Make a Payment.
5)Click on the Amount field and enter an amount, then click done.


Actual results:

While I was doing the testing for Firefox for Android, I logged in to my banking website as part of the test. Everything was going well until I wanted to make a payment on my credit card. I was able to fill out everything, but when I went to enter the amount, ie 375.11, I could not click the done bottom on the bottom of the screen and the field box where typed the amount was red. Unable to continue, I canceled the payment and logged out.


Expected results:

After I had type the amount on the text field, I should have been able to click done and finish the process to make a payment on my credit card.

Comment 1

[Mark Capella [:capella]]

This WFM on my n5X/6.0.1 ... FF 48.0a1

Comment 2

[Kevin Brosnan [Ex-Mozilla]]

Works for me on a Nexus 5x with Firefox 45.0.2

Comment 3

[G-Sanchez10]

When i originally ran this on my phone LG G4 with Firefox 45.0.2 it would load the following url when i went to the Bank of America website: www.bankofamerica.com/mobile/banking.go?channel=mobile. But now when i go to the same website this url loads instead: https://www.bankofamerica.com/homepage/overview.go?MobileRedirect=false&channel=mobile

Comment 4

[Mark Capella [:capella]]

They both look like valid entry points to the bank (Secure, same cert info, etc).

I'd tested by typing |bankofamerica.com| into my addressbar, which brings me to your second URL
https://www.bankofamerica.com/homepage/overview.go?MobileRedirect=false&channel=mobile

I have screenshots I took along the way, but haven't tested the original entry point you mention.

Does the problem still exist? Does it occur on both sites? Can you test on a different device? Were you NSF in your funding account? (RED $amount?) etc...

Comment 5

[G-Sanchez10]

Attachment: image of issue

This a picture of the issue. One arrows shows the text box showing an error when i entered the amount. The other arrow points to the done button, which can't be pressed due to the red highlighted text box.

Comment 6

[G-Sanchez10]

the issue still exist with the first url: www.bankofamerica.com/mobile/banking.go?channel=mobile 
This loads up the mobile version of the page. I click the button on the top right corner to sign in to my account. Once i click the button the url then becomes as followed: https://staticweb.bankofamerica.com/cavmwebbactouch/common/index.html#home?app=signonv2 
It is from there that the page looks like the bank of america mobile app. It is from there when i try to do the payment that i get stuck when entering the amount and can't continue. On a previous comment i uploaded an image from my phone illustrating the issue.

Comment 7

[Mark Capella [:capella]]

Ah, well that's a numeric-only field. If I enter |13.45| for example it's happy.

If I copy a string like |$13.45| from somewhere to the clipboard and paste it into the field, I get the (RED / error) situation.

Try it with only a numeric transaction amount.

Comment 8

[G-Sanchez10]

Attachment: image of issue only with numbers

Still occurs even with only numbers

Comment 9

[Mark Capella [:capella]]

Ah, mmmm ... I hadn't bothered to press "done" before in my test, but once I do, I get the RED/error box also ...

I just tried on Chrome and this works to completion for me. I notice there seems to be some script management of the <input> field as the numbers are being formatted as I type in Chrome, and I didn't observe that visually in FF.

So there does appear to be an issue here.

Comment 10

[Mark Capella [:capella]]

Poking around, I see the page uses a script [0], that iiuic appears to reference global event, or window.event at [1], causing a page burp [2] everytime I tap a key, so part of their security seems to be intercepting keys but failing to process them.

This seems the culprit. I saw this previously in [3], which itself was an >OLD< dup to [4]. While Chrome, and Opera for example implement this, we do not, and wind up tossing to Tech Evangelism.


[0] https://staticweb.bankofamerica.com/cavmwebbactouch/common/js/libs/jquery-1.11.1.min.js
[1] function J() {
      (y.addEventListener || "load" === event.type || "complete" === y.readyState) && (I(), m.ready())
    }
[2] [JavaScript Error: "ReferenceError: event is not defined"
       {file: "https://staticweb.bankofamerica.com/cavmwebbactouch/common/js/libs/jquery-1.11.1.min.js line 2
        > eval" line: 1}
    ]

[3] Bug 1185099 - UI / Touch widget behavior fails on Fennec
[4] Bug 218415 - Request for window.event object added to DOM to ease cross browser scripting

Comment 11

[Hallvord R. M. Steen [:hallvors]]

The lack of window.event support is not unlikely to be the problem but it's not proven yet - right?

Comment 12

[Mark Capella [:capella]]

It's likely the cause, but not proven. I'm running a debug build and watching them drop eKeyUp events.

Comment 13

[Mark Capella [:capella]]

My ex, who's an SVP of Software Dev for BOA suggests we could simply call their customer service to report it:

Mobile Banking customer support
1.800.933.6262

I wonder if this is an issue worth pursuing, as the old URL seems to no longer be automatically offered through the website, and the one that is, works.

Comment 14

[Hallvord R. M. Steen [:hallvors]]

Attachment: fake-win-event-extension.xpi

I've written an extension to shim window.event support in Firefox Android - might help verify that this is the issue (hope it works correctly)

Comment 15

[Mark Capella [:capella]]

Indeed, the shim resolves the JavaScript error and allows a payment to be made, seeming to resolve this bug.

Additionally, the page with the slider issue [0] also works with this fix, though it's quite slow compared to the performance of Chrome.


[0] http://space.gizmodo.com/this-shower-of-gamma-rays-are-from-a-flaring-blazar-5-b-1717123013

Comment 16

[Mike Taylor [:miketaylr]]

This should be fixed now that we've implemented window.event.