UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. using the contentSettings API, set a block rule for your camera.
2. go to a website that will try to use your camera, such as https://davidwalsh.name/demo/camera.php

What is the expected behavior?
the expected behaviour is that because there is a block rule in place, the browser won't ask the user to allow or block the camera.

What went wrong?
the browser asks the user to allow or block the camera, in essence it uses the default "ask" rule and ignores the block rule. if the block rule were in place, i'd expect to see an icon in the address bar that usually appears when plugins/content settings are blocked.

based on previous bug reports, i'm starting to wonder how much of the contentSettings API works as documented...

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 56.0.2924.87  Channel: stable
OS Version: OS X 10.12.3
Flash Version: