I embedded the images into your post instead. : )
I tried it out in Edge and wasn’t able to replicate the issue though - it does narrow the search down to WV for me. Do you see it searching for results in the Location dropdown when you type there?
And do you have any browser extensions that could be interfering with it? You might try opening a new InPrivate window to test.
Thanks for checking on this.
I do get “West Virginia” in the drop-down list in all browsers.
I tried a private window, but I got the same results - no search by state is generated in Edge.
I also tried FF and the search was successful.
Thanks,
-Mike
Javascript is the programming language used on websites. Different browsers handle Javascript commands differently, which results in things working in one browser but not other browsers.
You can use the developer tools in Edge to check if there are any Javascript errors. Here’s a video about using the developer tools. At the 2:30 minute mark, they talk about “console” tab, and show a lot of red error messages.
https://www.youtube.com/watch?v=R4-kwFCpXG4
Open the developer tools in Edge. When you do a search, do you see red error messages?
your Edge screenshot seems to have an extra white margin on the left that i wouldn’t expect to be rendered. are you using a really old version of Edge? are you using it from some really old machine and OS?
I am using:
Microsoft Edge is up to date.
Version 149.0.4022.80 (Official build) (64-bit)
Thanks.
There are no error messages of any kind.
I choose the species and the state and then click on “Go”.
Nothing happens at all.
Here is the error message from the Edge Developer Tools:
====
places.js:687 As of March 1st, 2025, google.maps.places.Autocomplete is not available to new customers. Please use google.maps.places.PlaceAutocompleteElement instead. At this time, google.maps.places.Autocomplete is not scheduled to be discontinued, but google.maps.places.PlaceAutocompleteElement is recommended over google.maps.places.Autocomplete. While google.maps.places.Autocomplete will continue to receive bug fixes for any major regressions, existing bugs in google.maps.places.Autocomplete will not be addressed. At least 12 months notice will be given before support is discontinued. Please see https://developers.google.com/maps/legacy for additional details and https://developers.google.com/maps/documentation/javascript/places-migration-overview for the migration guide.
Qm @ places.js:687
places.js:83 As of March 1st, 2025, google.maps.places.AutocompleteService is not available to new customers. Please use google.maps.places.AutocompleteSuggestion instead. At this time, google.maps.places.AutocompleteService is not scheduled to be discontinued, but google.maps.places.AutocompleteSuggestion is recommended over google.maps.places.AutocompleteService. While google.maps.places.AutocompleteService will continue to receive bug fixes for any major regressions, existing bugs in google.maps.places.AutocompleteService will not be addressed. At least 12 months notice will be given before support is discontinued. Please see https://developers.google.com/maps/legacy for additional details and https://developers.google.com/maps/documentation/javascript/places-migration-overview for the migration guide.
I7 @ places.js:83
main.js:410 As of February 21st, 2024, google.maps.Marker is deprecated. Please use google.maps.marker.AdvancedMarkerElement instead. At this time, google.maps.Marker is not scheduled to be discontinued, but google.maps.marker.AdvancedMarkerElement is recommended over google.maps.Marker. While google.maps.Marker will continue to receive bug fixes for any major regressions, existing bugs in google.maps.Marker will not be addressed. At least 12 months notice will be given before support is discontinued. Please see https://developers.google.com/maps/deprecations for additional details and https://developers.google.com/maps/documentation/javascript/advanced-markers/migration for the migration guide.
Qm @ main.js:410
Yellow warning messages are fine. We are looking for red error messages. Since you didn’t see red errors, something else is wrong.
Click on the “Network” tab in the Developer Tools. In the “Filter” text box, enter in “api.inaturalist”. Click the “Fetch/XHR” button. This will show all connections made to the iNaturalist API. Click the circle with slash button to clear the log.
When you type in the species names, you will see some connections with name “autocomplete?..”. When you select the species, you should see connections named “observations?..”, “species_counts?..” . Click the circle with slash button to clear the log.
Type in the place name, and select the place. Do you see connections made to “observations?..”, “species_counts?..” ?
Here’s a screenshot of Chrome dev tools, network tab after selecting “West Virginia” from the drop down menu.
I am using Edge, not Chrome.
This is waaay to complex for me to follow.
Thanks for your efforts.
-Mike
if you’re using the latest version of the browser, then i can only guess that you’ve got something strange in your own setup. it’s likely something that only you can troubleshoot, since no one else is currently able to reproduce the issue, and there’s no good way to guess how your setup might differ from default / usual setups. there’s really no good reason why most of the page should work for you except the location filter.
my only suggestion for you is that you’re probably better served by using the Filters > More Filters > Places filter over the Location filter anyway. see: https://forum.inaturalist.org/t/search-engine-with-problems-with-word-brazil/28136/26
