Die Batzen

In lists (bookmark and ignore) the displayed distance value less than 1km/mi is wrong. For distances greater or equal to 1km/mi it is correct. Appended are two screenshots that show the issue when comparing the same results in bookmark list and search: the first three caches are less than 1 km away from the home coordinates (in this case HQ), but show distances in the bookmark list that are too high by a factor of 1000.

Well, it looks like the old search page is already partly out of business: https://www.geocaching.com/seek/ Some searches still show results as we know it (e.g. by Address), but others redirect to the new search page without showing any results at all, e.g.: by State/Province by Country Cache Starts with by Areacode Found by Username Hidden by Username Is this intended?

Have a look here: https://api.Groundspeak.com/documentation#referencecodes

BUG: continuous CPU load on Firefox, Windows 10, Desktop On https://www.geocaching.com/plan/lists there's a continuous CPU load using Firefox on desktop (>10% on a Laptop) - even if the page is fully loaded. As soon as one switches to a different tab the CPU drops immediately to <1%. Switching back to the lists tab and the CPU load is back. This is also the case on any list detail view. No browser add-ons are running. On Chrome this seems not to be an issue.

How about adding the Watchlist to the new Lists experience? It's a list and would complete the experience.

BUG on Firefox 63.0.3 (64-bit): go to new map settings and increase the number of caches shown on the map to either 750 or 1000 zoom out until you exceed this limit ensure that you clicked on "Search this area" to update map view and search results now try e.g. to zoom in/out, move the map, step through the search pages - the result is always the same: the Firefox window gets completely white, everything's gone even a refresh doesn't help On Chrome this is not an issue.

The new map is constantly causing high CPU usage of the browser. As soon as you switch to another tab CPU usage is back to normal. This holds true for Firefox and Chrome (actual versions).