[SOLVED] Chrome warnings

Help & Support
1

Recently I see these warnings in chrome. Should I do something with that?

[Violation] ‘requestAnimationFrame’ handler took 584ms

[Violation] Added non-passive event listener to a scroll-blocking ‘mousewheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See Passive event listeners - Chrome Platform Status

[Violation] ‘message’ handler took 213ms

2

Hi @Albertos,

Most likely you’ve enabled that console message type to be printed in the Chrome console. From a StackOverflow thread:

“Chrome violations” don’t represent errors in either Chrome or your own web app. They are instead warnings to help you improve your app. In this case, Long running JavaScript and took 83ms of runtime are alerting you there’s probably an opportunity to speed up your script.

(“Violation” is not the best terminology; it’s used here to imply the script “violates” a pre-defined guideline, but “warning” or similar would be clearer. These messages first appeared in Chrome in early 2017 and should ideally have a “More info” prompt to elaborate on the meaning and give suggested actions to the developer. Hopefully those will be added in the future.)

1 Like