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

Crosshair ghosting is back after Chrome 59 update #318

Open
maeeast opened this issue Jun 27, 2017 · 1 comment
Open

Crosshair ghosting is back after Chrome 59 update #318

maeeast opened this issue Jun 27, 2017 · 1 comment

Comments

@maeeast
Copy link

maeeast commented Jun 27, 2017

I had a graph that was working fine before my chrome updated (and is still working fine in IE and FF). In chrome 59 the crosshair ghosting issue has returned. Does anyone know what in the chrome update broke this or have a fix for it?

@maeeast
Copy link
Author

maeeast commented Jun 27, 2017

I fixed the issue in my deployment of flotr2.js by changing:
5316 octx.save();
5317 octx.strokeStyle = options.color;
5318 octx.lineWidth = 1;
5319 octx.beginPath();

to

5316 octx.save();
5317 octx.strokeStyle = options.color;
5318 octx.lineWidth = .5;
5319 octx.beginPath();

That seems to fix the issue with the crosshair path leaving a trail.

Fransan pushed a commit to Fransan/Flotr2 that referenced this issue Aug 3, 2017
Moved clearRect  one pixel to the left to match lineWidth. Made clearRect 2px wide to make sure both sides of the line path are cleared.
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

1 participant