Nothing has changed in M61 so I don't think this is related to feature policy. Could you provide an example of what's not working? Thanks!

@raymes@chromium.org hi.

1. Install this extension : https://chrome.google.com/webstore/detail/mcgraw-hill-education-scr/pfcmainhppajoghlkioahfpepnlibicc

2.This is the test page i just have created for you: https://talya.tegrity.com/qar/oleg/test_cross_origin_ifram_getUserMedia.html

You can see it works fine without iframe.

3.Here is jsfiddle with testpage launched from iframe: https://jsfiddle.net/f3ty5wjh/

Open developer tools and see console.

Hi there,

This is a known restriction with the way the API works. Please see https://stackoverflow.com/questions/26424366/google-chrome-screen-capture-failing-when-iframe-is-used-same-script-works-wi

Please let us know if that resolves the issue. Closing as WontFix for the time being. Thanks!

@raymes@chromium.org thanks. I tested it with fixes from stackoverflow and it works well. 


I still see the depreciation warning :
"getUserMedia (camera) usage in cross-origin iframes is deprecated and will be disabled in M63, around December 2017. To continue to use this feature, it must be enabled by the embedding document using Feature Policy, e.g. <iframe allow="camera" ...>. See https://goo.gl/EuHzyv for more details."

1.We not using camera here (wrong message)
2.<iframe allow="camera" ...> - This change in December 2017 will work for screen?

Thanks in advance

At the point the deprecation warning is shown, it's not possible to detect what is being requested. Rest assured that screen capture will continue to work for the time being.