[Collection] Small lines on tile borders

[roopekoo]

Server Information

• [x] Latest Spigot Plugin
  • Version: Dynmap v3.0-beta-3
  • Server: Spigot 1.13.2
• [ ] Latest Forge Mod
  • Version:

• I can reproduce this issue consistently
  • [x] In Multiplayer
  • [ ] After deleting/renaming the DYNMAP folder
• [x] I have searched for this issue previously and it was either (1) not previously reported, or (2) previously fixed and I'm having the same problem.
• [ ] I am crashing and can provide my crash report(s)
• I have tried the following diagnostics;
  • [x] Re-rendered missing chunks using /dynmap fullrender
  • [x] Cleared cached tiles using /dynmap purgeworld [world] (especially if using a map from an older version)
  • [ ] Deleted/Renamed the dynmap folder to regenerate configs and files fresh
  • [ ] Tested using the 'HEAD' version from dynmap.us/builds (these are stable to use)
  • [ ] Rechecked the Minecraft Server and Web server Config (If using an external Web server)

Issue Description

My map's rendered tiles seem to be lazy to remove those transparent black borders from each tile. Happens when I zoom in or out and the map redisplays the tiles but leaves straight one-pixel-wide lines between each tile. If I move my view either vertical or horizontal lines disappear. Seems to be happening only with my 4K screen.

Reproduce Steps

1. Have the map rendered
2. Zoom in/out so the tiles must appear
3. Visible at least in my 4K display

Additional Information

Image with those black lines: https://imgur.com/n4w2L65

[Synt3x]

@roopekoo what web browser are you using? Have you tried any other web browser?

[roopekoo]

I currently use Brave browser. This "bug" happens with Brave, Chrome but not Edge, or Firefox. Might be chromium based problem...

[korhox]

I'm having same issue here. This happens on:

• Google Chome version: 75.0.3770.80
• Opera Developer version: 63.0.3340.0

This problem does not appear on Microsoft Edge, it does not seem to support 4K at all (blurring happens).

[FedUpWith-Tech]

Renaming for better management

[prenetic]

Now that Edge is based on Chromium, the same behavior can be seen across both Chrome and Edge.

[JurgenKuyper]

Looks like the problem we currently experience is because of the underlying leaflet.js. there is a pull-request to fix it, we just have to wait until it is implemented.