Steps to reproduce the problem:
(1) Create a page with a single <div ontouchstart='navigator.vibrate([150]);'>test vibrate</div>
(2) Tap the element
(3) Tap the element a second time

What is the expected behavior?
The phone/device will vibrate twice.

What went wrong?
Chromium disables vibrate until the user causes an onlick event.

Did this work before? Yes 

Chrome version: 64.0.3282.186  Channel: beta
OS Version: 66.0.3359.67 (Official Build) beta (32-bit)
Flash Version: 

I am trying to make my website act as close to an app as possible.  If the first interaction on the webpage is a longpress on an element for additional options, the experience feels largely incomplete without a vibration.

I am suggesting that if the user goes directly to the page (entered the URL directly) or if the user intentionally navigates to the page through an authenticated portal (such as a google search) that vibration is allowed from a touchstart event.

I feel like by requiring an onclick event first will just cause developers to mar the user experience by, for example, having a pop-up always appear to make sure that all features are activated or by just completely unusing certain features like vibration because they're unreliable... and we would end up pushing people to use an app instead of using the browser.