Payment page error on healthpost.co.nz
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(firefox66 affected)
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | affected |
People
(Reporter: lim.leong, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
At the final checkout page on healthpost.co.nz. I completed entering all information required for check out. Click on proceed and got an error - "Please specific courier type.". On the screen, the courier type service is clearly checked so the error is very strange. At that point I cannot proceed any further with the transaction.
Using Microsoft Edge for exactly the same transaction is fine so it is a Firefox issue. Quite some time ago I also reported a payment page bug with Firefox 64 on www.landsend.com. Similar sort of issue with the final payment page cannot proceed.
Actual results:
See above.
Expected results:
The final check out page shoud be completed.
The Landsend.com payment issue. I cannot remember the version of Firefox correctly. I stated 64 but it could be an earlier version. It is definitely a version 6 something issue.
|
||
Updated•7 years ago
|
|
||
Comment 2•7 years ago
|
||
I've tested this report on Windows 10 using the latest Nightly, Beta and Fx release builds. I did not manage to reproduce the mentioned behavior. Im using a CC generator. The website is displaying a message to verify my CC. Hence Im not sure what will be the behavior when using a valid CC.
Reporter, can you please retest this using the latest Nightly build (https://nightly.mozilla.org/) and report back the results? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E).
Hi Stefan. Unfortunately I am not in a position to re-test this because it require a real credit card transaction. As per your advice and I have a clear cache and clear forms data. I suspect it is a "sticky" form data problem which Firefox is not handling correctly because the the exact same transaction works fine on Edge browser.
|
||
Comment 4•7 years ago
|
||
If we can't reproduce, there's not much we can do unfortunately. Thanks for the report though.
Description
•