Websites have differences between Firefox and Safari
I recently viewed aa.com in Firefox. Was having trouble with linked pages and switched to Safari. Not only did the linked pages work in Safari, but there was a difference in the homepage, as well. Why would this happen? Not sure whether to switch back, because of inconsistency of sites working well in Firefox.
All Replies (7)
What is the issue? Provide steps to replicate the issue and screenshots.
In Firefox I went to aa.com. Logged in. Clicked on "AAdvantage", then "AAdvantage Credit Cards". Clicked on "learn more" under any of the credit card options and was taken to a page stating PAGE NOT FOUND 404...
I will attach a screenshot.
When I follow the same route in Safari, I'm taken to a page with the information I'm looking for.
I will attach a screenshot of that as well.
I do not understand why this is happening. Can I trust Firefox to give me an accurate web experience? My Firefox is up to date, so that is not the issue.
I prefer Firefox, but if I can't trust the experience, then I will have to switch back to Safari.
Thanks for your help!
Thank you for the steps. I don't have a login, but let me see if I can create one. Did you try the same steps with Firefox in Safe Mode? https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#w_how-to-start-firefox-in-4troubleshoot-modesf5safe-modesf
I created an account and had no issue with the site. I was able to "Learn More" about each card offer. see screenshotss
Modified
Is there anyone else that can help with this? I've logged in to both my account and my husband's account on aa.com using Firefox and get the same result - I get the "page not found" window.
This doesn't happen to me while using Safari.
I appreciate the attempt to help from jonzn4SUSE, but the fact that it works for jonzn4SUSE doesn't change my result while using Firefox.
I'm using Firefox on a Mac.
OK. NOW I figured it out. I'm using DuckDuckGo and it was blocking something on the aa.com site.
That's why I asked you to run Firefox in Safe Mode to see if it was an add-on causing the issue. ;-/