UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
Use `element.addEventListener("touchstart", code, {passive:false})`

The console is being spammed with verbose lines:

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

What is the expected behavior?
No log spam because `{passive:false}` has been explicitly added.

What went wrong?
I have thousands of pages for education, due to not being able to know until the touch/click what is meant to happen there is no way of telling the element that it will not be able to scroll beforehand, nor can the event be passive as it may need to be cancelled. Some pages have upwards of 5k of these on them, and result in just as many completely unnecessary spam lines being written to the log. When editing the pages via the a app that can result in >100k spam lines in a matter of minutes, causing the browser tab to crash.

Did this work before? Yes 58?

Chrome version: 60.0.3112.90  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Report *once* at most per source line calling it.

If a developer has specifically set `passive:false` then stop punishing the users by causing their browsing session to crash (especially when it's school age children). We've already had to redeploy thousands of pages when they stopped working from the surprise break from the web standards by setting `passive:true` without any spam lines like this...