User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 Build ID: 20160726073904 Steps to reproduce: 1.Go to http://amazon.in on any Laptop 2.Search and select any product 3.Click Select a delivery address below "Deliver to:" label on the RHS. 4.A pop form is displayed with the option of signing in or just enter the PINCODE. 5.Enter any valid PINCODE in India (Example : 569978, 440018...6 digits) 6.Click update Actual results: An error message is displayed: : "Please enter a valid 6 digit PINCODE !! Expected results: The form should update the delivery address and display the delivery time for the entered new address (PINCODE). Not happening with any other browser. Not sure if its a Firefox issue or amazon webpage issue!!
entering 569978 shows "Please enter a valid 6 digit pincode." on Firefox, Safari, and Chrome. entering 440018 updates the address to "Deliver to: NAGPUR, MAHARASHTRA 440018" on Firefox, Safari, and Chrome. is 569978 valid PINCODE?
569978 is not a valid pin code. 440018 is a valid pin code. I am still getting the same error in firefox.How can I upload a screen shot, please let me know.
1. Take a screenshot 2. Save it as a image file (png file is better) 3. Attach it to this bug from "Attach File" button above
Hi all, I have reported the bug to Amazon India also. The have send an email asking me to try again after 48 hours. They have escalated the issue. Thanks and Regards, Rocky
Tries with Firefox 48.0 on windows 10 but it doesn't happen. Does the issue happen with safe mode? https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
It is not happening in safe mode! The feature works correctly in safe mode.
Got it !! The https-everywhere addon is causing the issue. Once the addon is disabled the functionality works fine.
I have mailed firstname.lastname@example.org about the same. Thanks
I am not the subscribers list of email@example.com !! I got an automated reply that's it.
you could report the issue here https://github.com/EFForg/https-everywhere/issues/ anyway, it would be better tracking this issue on the extension's bug tracker, not here.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
QA Whiteboard: [bugday-20160808]
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.