maproulette3
maproulette3 copied to clipboard
Markers in Nearby tasks map not selectable on first click, and show double number of markers.
A contributor to this challenge shared this with me, and I confirm the issue.
After completing a task, selecting the nearby option, and clicking on the map - the action doesn't select the task and instead displays the markers twice, and only after then can you select a marker.
State | Screenshot |
---|---|
Initial view after selecting nearby option after task completion, showing tasks in the vicinity. | ![]() |
User clicks on a marker, to select a task . Nothing happens. Markers now displayed twice. | ![]() |
User clicks on a marker again. A marker is selected. "Doubles" disappear from view | ![]() |
After selecting a marker, it's always the one below it that disappears. Even if you click on the marker below (which disappears after clicking), you end up selecting the marker above it.
This is not a new behavior, having consistently experienced this before.
Thanks for the report, @govvin ! I haven't been able to reproduce this is any browser (even on that challenge). Do you know if there are any particular circumstances or set of actions that consistently lead to it happening?
I tried with Firefox and Safari on Mac and couldn't reproduce either...
Can you tell us more about the environment (OS, Browser + version) on which it reproduces?
I was planning to send a video capture of how this is happening, but for some reason I am unable to replicate this at all today.
I'm currently on Pop!_OS 20.04 LTS (I also experienced this previously on Ubuntu 18.04) using Firefox 79. A user using Firefox v68 on Ubuntu also reported the same, but curiously, they couldn't replicate this, too. I will update this thread again in a few days.
This seems to be an intermittent issue. I haven't personally experienced this in the last few days, but another contributor sent me their screen recordings of how it happened to them just some hours ago.
@govvin I'd definitely be curious to know if you continue to see any weird map marker behavior after today's release of v3.7.0
@nrotstan , I will try to take note of that peculiar behavior. :+1:
@govvin I'd definitely be curious to know if you continue to see any weird map marker behavior after today's release of v3.7.0