You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Magento Version: 2.3.1 (Commerce)
Module Map Version: 1.1.6 (in addition to store locator extension)
Environment: Production mode
Configured provider: Google Maps
Steps to reproduce
Go to stores page.
Put not exact address related to the list of markers and click "Search".
For instance, "Midland Highway, Kempton TAS, Australia"
Check map behavior.
Put exact address related to the list of markers and click "Search".
For instance, "3121 Midland Highway, Kempton TAS, Australia"
Check map behavior.
Expected result
The map is moved to corresponding area and related markers are displayed for both 3 & 5 steps.
Actual result
The map is moved to corresponding area and related markers are displayed for step 3.
The map is reset for step 5, all markers are displayed.
It looks like the extension expects to retrieve geometry.bounds for every result from Google Maps API during geocoding. In some cases it is not present, so the map is reset according to the current implementation. Probably geometry.viewport data could be used instead or as a fallback.
The text was updated successfully, but these errors were encountered:
Preconditions
Magento Version: 2.3.1 (Commerce)
Module Map Version: 1.1.6 (in addition to store locator extension)
Environment: Production mode
Configured provider: Google Maps
Steps to reproduce
For instance, "Midland Highway, Kempton TAS, Australia"
For instance, "3121 Midland Highway, Kempton TAS, Australia"
Expected result
The map is moved to corresponding area and related markers are displayed for both 3 & 5 steps.
Actual result
It looks like the extension expects to retrieve geometry.bounds for every result from Google Maps API during geocoding. In some cases it is not present, so the map is reset according to the current implementation. Probably geometry.viewport data could be used instead or as a fallback.
The text was updated successfully, but these errors were encountered: