Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Many antPaths in Chrome cause "flashing" effect #137

Open
1 of 6 tasks
haydenseitz opened this issue Jun 17, 2020 · 8 comments
Open
1 of 6 tasks

Many antPaths in Chrome cause "flashing" effect #137

haydenseitz opened this issue Jun 17, 2020 · 8 comments

Comments

@haydenseitz
Copy link

haydenseitz commented Jun 17, 2020

Type:

  • bug
  • feature
  • question
  • enhancement

Environment:

  • OS: Windows 10
  • Browser: Chrome
  • Library Version: 1.3.0 (npm)

I'm going to open a PR:

  • yes
  • no

Description:
When adding many (150+) antPaths to a map that are not paused, there is a flashing effect that happens when viewed in Chrome. This does not happen in Firefox or Edge

Here's an example HTML:
leaflet-antpath-flashing-example.zip

GIF of example HTML in Chrome:
leaflet-antpath-flashing-example-chrome

GIF of example HTML in Firefox:
leaflet-antpath-flashing-example-firefox

@ruan1998
Copy link

I am also confused about this problem.

1 similar comment
@FortunaBEE
Copy link

I am also confused about this problem.

@emilmahler
Copy link

I can confirm the same issue in the Leaflet.extras2 package for R that uses this plugin.

@MrOttimista
Copy link

I tried this on chrome and I couldn't produce the bug
my chrome version is Version 84.0.4147.105

@emilmahler
Copy link

The bug occurs in version 84.0.4147.135 and 85.0.4183.83. @MrOttimista can you try upgrading? So maybe this bug was introduced with the newer versions of Chrome.

@jspyhotdev
Copy link

I tried with this sample html code. it was working.
var pathOpts = {
lineCap: 'butt'
, delay: 2000
, reverse: false
, paused: false
, renderer: L.svg({ pane: "overlayPane" })
}

@ontwikkelfabriek
Copy link

ontwikkelfabriek commented Feb 12, 2021

any progress on this.... It's still occurring in the latest Chrome Version 88.0.4324.150 (Official Build) (64-bit)

It makes this wonderful plugin almost completely unusable.

@pazhukh
Copy link

pazhukh commented Dec 8, 2023

Same problem with the freshest Version 120.0.6099.71

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants