plotly.js: Chrome is logging [Violation] errors in verbose console mode

First reported https://community.plot.ly/t/violation-at-console/4518/7

To see it, open up https://codepen.io/etpinard/pen/ZyLQYy and turn on Verbose mode

image

The error message points to this line in dragbox.js.

[Violation] Added non-passive event listener to a scroll-blocking 'wheel' event. 
Consider marking event handler as 'passive' to make the page more responsive.

Observed in Chrome 59 and 58.


Anyone know what this is about?

About this issue

  • Original URL
  • State: open
  • Created 7 years ago
  • Reactions: 4
  • Comments: 28 (15 by maintainers)

Most upvoted comments

Any updates on this?

All examples of choropleth from https://plot.ly/javascript/choropleth-maps generates multiple messages:

[Violation] Added non-passive event listener to a scroll-blocking ‘touchstart’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952

My version of Chrome is 66. The messages are generated when I double click on any country. However, the example with Mapbox doesn’t generate any messages…

Did this ever get fixed…? My events are crashing when I try to perform some logic… I just get TONS of events.

Also wondering the status of this!

@dfcreative you’re going for this?

cc @dfcreative , which might know what this is about.

Let’s see… this is a pretty good description of how to detect and apply it: https://github.com/WICG/EventListenerOptions/blob/gh-pages/explainer.md