Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Chrome is logging [Violation] errors in verbose console mode

See original GitHub issue

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

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?

Issue Analytics

State:
Created 6 years ago
Reactions:4
Comments:28 (15 by maintainers)

Top GitHub Comments

2reactions

alexandertucommented, Jun 21, 2018

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…

2reactions

efadencommented, Sep 5, 2017

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

Top Results From Across the Web

Log messages in the Console - Chrome Developers

Learn how to log messages to the Console. ... Each console.* method is assigned a severity level: Verbose , Info , Warning ,...

Chrome Browser debug logs - Google Support

You can troubleshoot problems with Chrome Browser, such as hanging tabs and error messages. Use debug logs to help you. These logs aren't...

Hiding violations in Chrome Dev Console - Stack Overflow

Yes, as of Chrome 58: The Hide violations checkbox is gone. Set the logging level dropdown to Verbose to see violations.

Console Violations - Chrome DevTools - Dev Tips

Click the 'Default levels' dropdown in the Console Panel and select 'Verbose'; Type in violation in the Console Panel filter box. Violations can ......

What happened to the Developer Tools console?

@chromium.org> wrote: If you select Log, you see errors. The drop down configures the verbosity filter like in pretty much all ...