I can't anymore
I have loved FF desktop browser since I started using it per my boss in 2003. But I am so tired of the fact that EVERY SINGLE TIME you put out an update it breaks my access to the bank. EVERY SINGLE TIME. I waste HOURS reading articles, calling the bank IT dept, chatting with people who are on 3 calls at once, only to hear them tell me to "just use chrome." I clear the cookies, clear the cache, reboot, follow all the prompts in the settings and THEN the damned bank server doesn't recognize the device so it forces yet ANOTHER password change. It happened again TODAY and it makes me so sad but I cannot do it anymore. I am STILL now (going on 4 hours) trying to access the billpay page @ Xantanderbank. (ahem, secure codename) I am forced now, by this craziness, to use the imbecilic duckduckgo which is A) and offensive name and b) you KNOW it nowhere near the product you have built but I CANNOT DO THIS ANYMORE. Thank you for the time it takes to read this diatribe. I appreciate it.
Giải pháp được chọn
Hey cmaloof, thanks for taking the time to write in about this. If it has gotten to a point this frustrating please use whatever browser is easiest to use to access your banking needs. Over the last 2 years it seems certain banks are giving Firefox users more and more trouble just to login properly. I believe its due to their web development teams not testing for Firefox anymore or cutting the team's budget for testing in Firefox browsers and to only focus on Chrome, Edge and Safari.
That's what I believe the real problem is as not every Firefox update touches code that would upset a banking site that badly. The only big thing that changes is the useragent string. It's a line of code that tells the website what browser you are using and what version it is. Some websites don't update themselves to recognize the newer Firefox releases.
Anyway we really appreciate you being a Firefox user since 2003! That's longer than me. I started in 2004. :) Hopefully you can come back sometime in the future where your bank is properly working with Firefox again. But in the meantime, just use whatever helps you keep your sanity & frustrations low. I've noticed the web is getting way too complicated. So, for example, get ready when that next new thing called "Passkeys" (supposedly a replacement for passwords) arrives. ;)
Đọc câu trả lời này trong ngữ cảnh 👍 1Tất cả các câu trả lời (7)
Giải pháp được chọn
Hey cmaloof, thanks for taking the time to write in about this. If it has gotten to a point this frustrating please use whatever browser is easiest to use to access your banking needs. Over the last 2 years it seems certain banks are giving Firefox users more and more trouble just to login properly. I believe its due to their web development teams not testing for Firefox anymore or cutting the team's budget for testing in Firefox browsers and to only focus on Chrome, Edge and Safari.
That's what I believe the real problem is as not every Firefox update touches code that would upset a banking site that badly. The only big thing that changes is the useragent string. It's a line of code that tells the website what browser you are using and what version it is. Some websites don't update themselves to recognize the newer Firefox releases.
Anyway we really appreciate you being a Firefox user since 2003! That's longer than me. I started in 2004. :) Hopefully you can come back sometime in the future where your bank is properly working with Firefox again. But in the meantime, just use whatever helps you keep your sanity & frustrations low. I've noticed the web is getting way too complicated. So, for example, get ready when that next new thing called "Passkeys" (supposedly a replacement for passwords) arrives. ;)
Good morning, NoahSUMO,
Thank you for your kind reply and for helping resolve my berserked-ness. It is most appreciated.
Considering your answer and now that I think about it, it seems kind of "telling" that the bank already had a Why can't I get to that section page built in? It's like they KNOW there are problems coming but they can't be bothered to fix them? Are there too many variables for them?
When I get a bank employee about a page issue on the site, if it's an experienced tech or an agent that's been on the phones a few hours that day they will ask, "Which Browser?" The FF answer may get a "Just use Chrome" totally unacceptable answer or an " I'll check with my supervisor." That usually means passing the call off and maybe I'm lucky enough to get someone who says, "Oh yeah, I've heard that a couple of times today. I'll write a trouble ticket for you and send it to IT." OR, "Yeah, I use FF myself at home, even though we are required to use XYZ here at work."
It may take a day or two before it's resolved on their end. No explanation, but clearly I'm not the only one telling them there's another issue. But WHYYYYYYY do we have to do that? That's in our customer job description now, I guess.
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! I hate the stupid ducks.
The nutty thing, in my mind, is that the 3 little CUs that I use do not ever have that problem. They ALWAYS know whether the issue is in my browser and how to fix it ( is it on their end or in my mind?) I wonder whether CU users are more inclined to be FF users so they do continue to test with FF?
There is one bank that forces a new password every time I log in with an "unrecognized device" or clear the cache and cookies and you know the drill. So after this last issue I've changed that PW 3 times in 4 hours.
It's as bad as CVS requiring two step authentication for my online order of chocolate Easter bunnies! I gave up on them and use Walgreens for the fun stuff, now.
PASSKEYS???? Lord help me! How can we get any more convoluted? Like the insane computer generated one time password things? Might as well go back to walking down the street to the bank and just getting cash with my driver's license ID. Cash still works, right? For now?
THANK YOU AGAIN for your kindness and all your work with the Fox.
cmaloof said
PASSKEYS???? Lord help me! How can we get any more convoluted? Like the insane computer generated one time password things? Might as well go back to walking down the street to the bank and just getting cash with my driver's license ID. Cash still works, right? For now?
I have trouble in the real world as I've never learnt to drive nor left the country so have neither a driving license nor passport.
In Britain these days you are very unlikely to find a bank within walking distance never mind a branch of the one you use.
We're super glad to find such a long lasting user of Firefox!
Thank you for keeping us up to date, development team is very appreciative of this and it helps us pinpoint the problem.
If possible, could you try reverting back to ETP Strict temporarily and telling us which trackers are being blocked?
Also, could you try setting the network.cookie.CHIPS.enabled pref in about:config to false, refresh the page and check if that fixes the issue?
If it does, could you than set the same back to true, refresh the page and confirm the error is still there?
This would greatly help our development team.
Thanks in advance, Dan
To circle back on this, development team found the issue and the fix is coming up soon. Thanks for your patience everyone!
We have just released an update - Firefox 131.0.3 that fixes this issue. Please make sure to update your Firefox. Thank you for reporting this and happy browsing!