X
Tap here to go to the mobile version of the site.

Support Forum

Airmiles.ca will not complete ticket purchase in Firefox 64.0 if set to Private Browsing mode! Ideas as to why?

Posted

Everything went well with the booking until I got to the last page where I review the booking and Air Mile Flights Terms and Conditions. "By clicking on this button, I have read the Travel Documentation Advisory and agree to the terms and conditions of the AIR MILES Reward Program". When I click that link the page proceeds to "PROCESSING Please Wait", then it quickly flashes to "Authorizing" and then reverts to the page that I just left. It never stops on the page where I would enter the Payment details.

If I disable private browsing the site functions properly and I can complete the transaction. Popups and cookies were allowed in both scenarios.

Windows 8.1

Everything went well with the booking until I got to the last page where I review the booking and Air Mile Flights Terms and Conditions. "By clicking on this button, I have read the Travel Documentation Advisory and agree to the terms and conditions of the AIR MILES Reward Program". When I click that link the page proceeds to "PROCESSING Please Wait", then it quickly flashes to "Authorizing" and then reverts to the page that I just left. It never stops on the page where I would enter the Payment details. If I disable private browsing the site functions properly and I can complete the transaction. Popups and cookies were allowed in both scenarios. Windows 8.1

Additional System Details

Installed Plug-ins

  • Shockwave Flash 31.0 r0

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0

More Information

jscher2000
  • Top 10 Contributor
8704 solutions 71122 answers

My guess would be the Tracking Protection function of the Content Blocking feature, which blocks embedded content from other sites that is associated with cross-site tracking. So that could affect some verification services and perhaps even payment processing scripts.

If you need to make a temporary exception to Content Blocking in a private window, you can use the "shield" icon at the left end of the address bar. But if you are redirected to a new payment site, then the exception would no longer apply, so the problem may reoccur there.

More info: Content blocking

My guess would be the Tracking Protection function of the Content Blocking feature, which blocks embedded content from other sites that is associated with cross-site tracking. So that could affect some verification services and perhaps even payment processing scripts. If you need to make a temporary exception to Content Blocking in a private window, you can use the "shield" icon at the left end of the address bar. But if you are redirected to a new payment site, then the exception would no longer apply, so the problem may reoccur there. More info: [[Content blocking]]