Kamil Monicz

I don't think this is a proper fix for the issue. Ideally, unused tiles should be disposed completely because higher zoom does not equal better experience. When zooming out, lower...

Yes, I know what you are talking about. I also have this problem. But in my opinion it's better to fix it instead of doing this z-index workaround.

The same as it is right now for non-timeouting tiles. Just dispose the unnecessary ones, instead of hiding them.

> Why should already loaded-in tiles be discarded in favour of lower resolution/detail tiles? Because higher resolution does not mean better experience. On some layers it's better to use lower...

Okay, now I can see the sense of using the z-index. :+1: Thanks!

Cool idea, I think the first delay should be slightly longer, e.g: 500ms, 250ms, 250ms, …. I believe a solution using [`setInterval`](https://developer.mozilla.org/en-US/docs/Web/API/setInterval) and `clearInterval` would be much cleaner and easier...

🙂! If you are interested, I use this package to run https://github.com/Zaczero/osm-countries-geojson. It finally resolved the issue with overlaps/gaps produced during the simplification process. And now [it's perfect](https://github.com/Zaczero/osm-countries-geojson/blob/main/geojson/osm-countries-0-1.geojson)!

1. This is simply the nature of OSM data. In regions of conflict, it's common to encounter such situations. Sometimes, you might even come across two countries at the same...

I have found a temporary workaround for those who are using _launch.json_. Perhaps it is possible to find a similar solution for a global case, but for me, _launch.json_ fix...

Just came across this ticket. Why do we need such a complicated policy? Just do: > Only editors that are widely popular, general-purpose, and compliant with OpenStreetMap's data policies may...