Ilias Tsangaris

Here's a `compilation-stats.json` file that repros the issue (apologies for it being rather large) [compilation-stats.json.zip](https://github.com/webpack-contrib/webpack-bundle-analyzer/files/7973733/compilation-stats.json.zip)

I was able to repro this issue on Mac in Chrome on react-hotkeys 2.0.0.

relates to #248, #215, & #232

https://github.com/greena13/react-hotkeys/issues/232#issuecomment-544253167 >I'm afraid my advice in the short term is to avoid any key combinations with alt in them.

@ChristoRibeiro why was this issue closed?

Yeah this confused me as well, basically `onStart` prevents any click event from continuing the event capture phase, while `onDrag` does not. Therefore changing to former to the latter fixed...

OK this [line of code](https://github.com/AbelHeinsbroek/chartjs-plugin-crosshair/blob/df67175e40cc3c860d7b74c2eb6d3bca0f0b494c/src/trace.js#L217) seems relevant. So that `chart.crosshair.enabled` flag works correctly, but the crosshair shows even when it is `false`. That would sense if `sync` is also enabled...

Hmm, so [this line](https://github.com/AbelHeinsbroek/chartjs-plugin-crosshair/blob/master/src/trace.js#L261) early returns and the crosshair becomes hidden if the mouse leaves the chart through the left or right border (moving along the x-axis); however, when the...

I believe this issue is resolved and can now be closed

> However your fix probably goes too far on very big displays or lower zoom settings @stefanct Yeah that's a good point—added a `max-width`.