It appears ever since Firefox 131 was released we're getting a lot of users in SUMO reporting they can't access the Bill Pay portion of their banks site. Of course, you don't need me to tell you that's very BAD. The affected banks seem to include various small credit union banks and big established banks like Bank of America, TD Bank and PNC Bank. As the last time I broke news this big, I'm not happy imagining thousands of Firefox users hitting this bug, getting angry, whipping out the pitchforks and marching down to support.mozilla.org to let us know that something important they use everyday broke yet again. As an aside, I think we're going to have to look at our QA practices here. Although QAing for all big banks and some small credit unions isn't easy sadly. I believe the mighty RyanVM stumbled upon this bug to back on Sept 9 in Bug 1918483. But I couldn't tell if he was on release, beta or nightly when he hit the bug. And I have seen a few scattered reports about broken Bill Pay as early as of August this year. I believe those were on credit union sites. My guess is that Enhanced Tracking Protection is blocking a script or cross-site cookie all of these banks use to conduct Bill Pay. Only 2 bank users were able to make Bill Pay work again by lowering the ETP to Standard. One of them had it on Custom prior. The rest claim changing ETP settings do nothing. Even totally disabling ETP and still having broken Bill Pay. Shooting up the flares to the great Relman team. Get the word out to whoever can help with this. :) ### **SUMO reports** 8-1-24; earliest report so far I am unable to use my bank bill pay with Mozilla as of 8/1/2024 https://support.mozilla.org/questions/1455863 National Bank of Middlebury (Vermont) user who solved Bill Pay breaking by reducing ETP to Standard: https://support.mozilla.org/questions/1455863#answer-1679337 https://cw411.checkfreeweb.com/imm/BrowserPolicy/NoCookiesEnabled/14726 https://nbmvt.com/convenient-banking/mobile-online-banking/bill-pay/ 9-1-24 - Unspecified bank with broken Bill Pay: https://support.mozilla.org/questions/1461518 Santander Bank user [solved by reducing ETP to Standard] (almost lost this user we've had since 2003!): https://support.mozilla.org/questions/1467195#answer-1679287 "And, to whom it may concern, I solved this most recent issue, finally, by clearing my custom settings and using "STANDARD" because the solutions the bank offered, along with my 2 customizations still did not work. And FTR I have written my diatribe about this to the bank as well as posting here. I WANT my FF back!" PNC Bank user [solved by reducing ETP to Standard]: https://support.mozilla.org/questions/1467900#answer-1680150 Bank of America Bill Pay reports (list keeps growing): https://support.mozilla.org/questions/1468068 https://support.mozilla.org/questions/1467853 https://support.mozilla.org/questions/1467420 https://connect.mozilla.org/t5/discussions/bank-of-america-s-bill-pay-does-not-work/td-p/73544 TD Bank Bill Pay reports: https://support.mozilla.org/questions/1467865 "Since the recent update to Firefox 131, I can no longer use the Billpay option of my TD Bank account. I am able to log into my account without any problems and use all of the options except for Billpay. I want to add that I know I am not alone with this problem as I have seen several others with the same problem but with different banks. It is the Billpay option which no longer works." https://support.mozilla.org/en-US/questions/1455863#answer-1680293 "With all add-ons disabled, Enhanced Tracking completely off, with the cache and data cleared this results in the same message as I and apparently many others are having. I have had this bank account for many years and it is just with FF 131 on Windows 11 that the problem has cropped up. Another user stated that he went back to 130 and all was fine until he again updated to 131 and the problem returned." ### Thoughts: I don't know about you all but I think we should backout the offending patch. RyanVM might be able to do a regression range hunt to see which Nightly first introduced the issue but I have a feeling someone is going to circle back and say its due to "network.cookie.cookieBehavior.optInPartitioning" (bug 1918483 comment #3). Which I have no idea what that is. Yet another cookie isolation feature?
Bug 1923500 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
It appears ever since Firefox 131 was released we're getting a lot of users in SUMO reporting they can't access the Bill Pay portion of their banks site. Of course, you don't need me to tell you that's very BAD. The affected banks seem to include various small credit union banks and big established banks like Bank of America, TD Bank and PNC Bank. As the last time I broke news this big, I'm not happy imagining thousands of Firefox users hitting this bug, getting angry, whipping out the pitchforks and marching down to support.mozilla.org to let us know that something important they use everyday broke yet again. As an aside, I think we're going to have to look at our QA practices here. Although QAing for all big banks and some small credit unions isn't easy sadly. I believe the mighty RyanVM stumbled upon this bug back on Sept 9 in Bug 1918483. But I couldn't tell if he was on release, beta or nightly when he hit the bug. And I have seen a few scattered reports about broken Bill Pay as early as of August this year. I believe those were on credit union sites. My guess is that Enhanced Tracking Protection is blocking a script or cross-site cookie all of these banks use to conduct Bill Pay. Only 2 bank users were able to make Bill Pay work again by lowering the ETP to Standard. One of them had it on Custom mode prior. The rest claim changing ETP settings do nothing. Even totally disabling ETP and still having broken Bill Pay. Shooting up the flares to the great Relman team. Get the word out to whoever can help with this. :) ### **SUMO reports** 8-1-24; earliest report so far I am unable to use my bank bill pay with Mozilla as of 8/1/2024 https://support.mozilla.org/questions/1455863 National Bank of Middlebury (Vermont) user who solved Bill Pay breaking by reducing ETP to Standard: https://support.mozilla.org/questions/1455863#answer-1679337 https://cw411.checkfreeweb.com/imm/BrowserPolicy/NoCookiesEnabled/14726 https://nbmvt.com/convenient-banking/mobile-online-banking/bill-pay/ 9-1-24 - Unspecified bank with broken Bill Pay: https://support.mozilla.org/questions/1461518 Santander Bank user [solved by reducing ETP to Standard] (almost lost this user we've had since 2003!): https://support.mozilla.org/questions/1467195#answer-1679287 "And, to whom it may concern, I solved this most recent issue, finally, by clearing my custom settings and using "STANDARD" because the solutions the bank offered, along with my 2 customizations still did not work. And FTR I have written my diatribe about this to the bank as well as posting here. I WANT my FF back!" PNC Bank user [solved by reducing ETP to Standard]: https://support.mozilla.org/questions/1467900#answer-1680150 Bank of America Bill Pay reports (list keeps growing): https://support.mozilla.org/questions/1468068 https://support.mozilla.org/questions/1467853 https://support.mozilla.org/questions/1467420 https://connect.mozilla.org/t5/discussions/bank-of-america-s-bill-pay-does-not-work/td-p/73544 TD Bank Bill Pay reports: https://support.mozilla.org/questions/1467865 "Since the recent update to Firefox 131, I can no longer use the Billpay option of my TD Bank account. I am able to log into my account without any problems and use all of the options except for Billpay. I want to add that I know I am not alone with this problem as I have seen several others with the same problem but with different banks. It is the Billpay option which no longer works." https://support.mozilla.org/en-US/questions/1455863#answer-1680293 "With all add-ons disabled, Enhanced Tracking completely off, with the cache and data cleared this results in the same message as I and apparently many others are having. I have had this bank account for many years and it is just with FF 131 on Windows 11 that the problem has cropped up. Another user stated that he went back to 130 and all was fine until he again updated to 131 and the problem returned." ### Thoughts: I don't know about you all but I think we should backout the offending patch. RyanVM might be able to do a regression range hunt to see which Nightly first introduced the issue but I have a feeling someone is going to circle back and say its due to "network.cookie.cookieBehavior.optInPartitioning" (bug 1918483 comment #3). Which I have no idea what that is. Yet another cookie isolation feature?
It appears ever since Firefox 131 was released we're getting a lot of users in SUMO reporting they can't access the Bill Pay portion of their banks site. Of course, you don't need me to tell you that's very BAD. The affected banks seem to include various small credit union banks and big established banks like Bank of America, TD Bank and PNC Bank. As the last time I broke news this big, I'm not happy imagining thousands of Firefox users hitting this bug, getting angry, whipping out the pitchforks and marching down to support.mozilla.org to let us know that something important they use everyday broke yet again. As an aside, I think we're going to have to look at our QA practices here. Although QAing for all big banks and some small credit unions isn't easy sadly. I believe the mighty RyanVM stumbled upon this bug back on Sept 12 in Bug 1918483. But I couldn't tell if he was on release, beta or nightly when he hit the bug. And I have seen a few scattered reports about broken Bill Pay as early as of August this year. I believe those were on credit union sites. My guess is that Enhanced Tracking Protection is blocking a script or cross-site cookie all of these banks use to conduct Bill Pay. Only 2 bank users were able to make Bill Pay work again by lowering the ETP to Standard. One of them had it on Custom mode prior. The rest claim changing ETP settings do nothing. Even totally disabling ETP and still having broken Bill Pay. Shooting up the flares to the great Relman team. Get the word out to whoever can help with this. :) ### **SUMO reports** 8-1-24; earliest report so far I am unable to use my bank bill pay with Mozilla as of 8/1/2024 https://support.mozilla.org/questions/1455863 National Bank of Middlebury (Vermont) user who solved Bill Pay breaking by reducing ETP to Standard: https://support.mozilla.org/questions/1455863#answer-1679337 https://cw411.checkfreeweb.com/imm/BrowserPolicy/NoCookiesEnabled/14726 https://nbmvt.com/convenient-banking/mobile-online-banking/bill-pay/ 9-1-24 - Unspecified bank with broken Bill Pay: https://support.mozilla.org/questions/1461518 Santander Bank user [solved by reducing ETP to Standard] (almost lost this user we've had since 2003!): https://support.mozilla.org/questions/1467195#answer-1679287 "And, to whom it may concern, I solved this most recent issue, finally, by clearing my custom settings and using "STANDARD" because the solutions the bank offered, along with my 2 customizations still did not work. And FTR I have written my diatribe about this to the bank as well as posting here. I WANT my FF back!" PNC Bank user [solved by reducing ETP to Standard]: https://support.mozilla.org/questions/1467900#answer-1680150 Bank of America Bill Pay reports (list keeps growing): https://support.mozilla.org/questions/1468068 https://support.mozilla.org/questions/1467853 https://support.mozilla.org/questions/1467420 https://connect.mozilla.org/t5/discussions/bank-of-america-s-bill-pay-does-not-work/td-p/73544 TD Bank Bill Pay reports: https://support.mozilla.org/questions/1467865 "Since the recent update to Firefox 131, I can no longer use the Billpay option of my TD Bank account. I am able to log into my account without any problems and use all of the options except for Billpay. I want to add that I know I am not alone with this problem as I have seen several others with the same problem but with different banks. It is the Billpay option which no longer works." https://support.mozilla.org/en-US/questions/1455863#answer-1680293 "With all add-ons disabled, Enhanced Tracking completely off, with the cache and data cleared this results in the same message as I and apparently many others are having. I have had this bank account for many years and it is just with FF 131 on Windows 11 that the problem has cropped up. Another user stated that he went back to 130 and all was fine until he again updated to 131 and the problem returned." ### Thoughts: I don't know about you all but I think we should backout the offending patch. RyanVM might be able to do a regression range hunt to see which Nightly first introduced the issue but I have a feeling someone is going to circle back and say its due to "network.cookie.cookieBehavior.optInPartitioning" (bug 1918483 comment #3). Which I have no idea what that is. Yet another cookie isolation feature?