consider loosening vibrate restrictions |
|||
Issue descriptionWe currently limit vibrate in subframes to frames that have had a user gesture. Shortly, we'll extend that to top-level pages as well. Should we hear sufficient developer demand, we could consider loosening those restrictions in careful ways. For example, we could create a vibrate-specific engagement score a la issue 700689 . This bug is just a placeholder for the discussion as we hear demand from developers.
,
Mar 21 2017
,
Apr 2 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 5 2018
I am for this.
,
Apr 5 2018
If a user goes directly to a website, for example, you should be able to cause a vibration if the first action is a long press on an element. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ojan@chromium.org
, Mar 13 2017