Search stops working when choosing a pinned location

When typing the name of a saved location I can’t make more then a couple mistakes in words before it stops working. For example, if I type “lakexx” and then delete “xx” the saved location “lake” won’t pop up, and if I delete everything and type anything again it won’t show any saved locations. It starts working again only if I close the map tab and reopen it.

1 Like

Can you please share a screenshot, and let us know which browser you are using? I can’t replicate on my computer.

Sure, in an hour. I’m using Google Chrome.
Hm, and when I want to make a screenshot it’s working perfectly. Sorry, it’s weird, this thing happened for me all the time.

@Marina_Gorbunova I’m not a developer but this is my impression: It can be due to how the edit box that you are typing it into triggers the lookup. When you type a new letter, it sends the changed lookup string, but if you backspace/delete, it doesn’t. If you were intending to type “lakehouse”, for instance, typing up to “lake” is sending the lookup text ok, but as soon as you type the x, the lookup text isn’t going to return results that match. That is expected, and as you say, you delete the x and would expect the results to show as if you had only typed “lake”, but it doesn’t. If you now press the space bar, or the next letter of the correct spelling (ie “h” making it “lakeh”, it will re-send the lookup text and you will get the results you expect.

I am only speculating that this is the problem and the cause and the solution. It is how I “picture” what is happening when I encounter it while entering a taxa in the 4x4 shortform and type either too quickly or backspace and change mid typing. Almost always, pressing space bar will immediately bring up the CV suggestions.


I understood how to deal with it, when it happens I need to click on another add, like scissors, then get back to browser and it will be working. Though I’d prefer if it wouldn’t happen at all.

Ok, an addition to this as nothing changed, it’s bugging when:

  1. type a wrong place name
  2. alt+tab (or open anything out of browser)
  3. get back and type any name - no responce if this place exist or not
  4. alt+tab back and forth again - it starts working again
    There’re probably other combinations of events too.
    image image
1 Like

what you’re describing sounds like some sort of throttling, but i can’t trigger any throttling on that autocomplete box myself. you’ve described in the past another situation that sounded like throttling ( that i also could not reproduce. so i’m thinking there’s something on your end – maybe your setup or maybe the process that you’re using to load your observations – that is causing these problems.

unfortunately, if no one can reproduce the problem reliably, then it will be really hard to help you, i suspect. if you can provide screenshots of your browser console messages and browser network activity, i think that could provide more clues.

1 Like