Bug: Sometimes the map shows incorrect area after typing a zipcode into search bar on landing page.

[fancyham]

• Please assign @fancyham and @Shienny1 to the PR

Describe the bug

Sometimes the map shows incorrect area after typing a zipcode into search bar on landing page.

This happens only sometimes!

Steps to reproduce the issue

In this video (turn on audio), taken at the beginning of July 2024:

Devlasite_searchbarbug.mp4

1. User typed in "90013"
2. Map shows an address in 90045 zip code (as seen in search address field at top of screen)

[fancyham]

@Shienny1 -- FYI, this is based on your bug report from this usability review spreadsheet: https://docs.google.com/spreadsheets/d/1dDZzrwRvulR-TyGP2Gj_NWhS5AzK_drQ5X3xpnuqOFY/edit?gid=0#gid=0

[SAUMILDHANKAR]

@Shienny1 Hi Shienny, I wanted to reach out to you since I am not able to reproduce this error. Maybe it got fixed as part of some other PR but just wanted to check how frequent did you notice the error, I tried around 10-15 times. Also, did the error appear on click or on pressing the enter key? I have noticed an error related to enter key but that may not be exactly related to this issue. Looking forward to hearing from you. Thanks.

[fancyham]

I was able to reproduce it right now on the public site and on devla on desktop by:

1. typing "90015" and quickly hitting return on the keyboard
2. which sometimes resolved to a 90045 address: "Los Angeles, California 90045, United States" in the search field but sometimes stayed "90015" in the text form field, and the map moves to 90045 anyway.

My guess is that whatever algorithm is powering the autocomplete, when the user hits the return key and doesn't select an auto-complete address, the autocomplete fails in unpredictable ways.

Video with audio:

Screen.Recording.2024-09-14.at.1.24.46.PM.mov

[Shienny1]

@SAUMILDHANKAR Yes this only happens on desktop, because of the speed of hitting "ENTER", just like @fancyham mentioned. I tried it on my mobile devices - this problem does not occur.

[SAUMILDHANKAR]

Thanks Bryan, Shienny for your help. I am able to reproduce the issue. I am looking into it and would share any update asap.

[SAUMILDHANKAR]

Reopening this issue since the PR #2223 solution didn't seem to work (as discussed in the meeting today). I will work on reverting the changes of the PR next.

[fancyham]

Please assign @fancyham and @Shienny1 to the PR