feature policy header causes Error saying vibrate is unrecognized
Reported by
oliverwi...@gmail.com,
Dec 3
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:63.0) Gecko/20100101 Firefox/63.0 Steps to reproduce the problem: 1. Create a feature policy which includes vibrate 'none' 2. See error in browser console 3. What is the expected behavior? What went wrong? console displays a message saying "Feature-Policy header: Unrecognized feature: 'vibrate'." This is particularly problematic seeing as the spec offers vibrate 'none' as an example. Did this work before? N/A Does this work in other browsers? Yes Chrome version: <Copy from: 'about:version'> Channel: stable OS Version: OS X 10.13 Flash Version: Shockwave Flash 31.0 r0
,
Dec 14
Chrome is behaving as expected, because there actually isn't a vibrate feature that can be controlled by Feature Policy. The example in the spec is misleading, an issue has been filed to update the spec: https://github.com/WICG/feature-policy/issues/263. |
||
►
Sign in to add a comment |
||
Comment 1 by dtapu...@chromium.org
, Dec 3