cc'd hta, who was the owner of  crbug.com/607439 , who might have some insights on this.

webkitGetUserMedia can probably be removed but hta should investigate.

lunalu, can you find or file another bug for and assign it to the storage component? Neither of these APIs are really related to frames. By the way, it is more useful to write  Issue 607439  than  crbug.com/607439  because Monorail will turn that into a link automatically.

Please see Issue 695494

Already unprefixed.

You perhaps want to remove the prefixed version, though

Filed https://github.com/webrtc/adapter/issues/712 about a problem with adapter.js that complicates removal.

you might want to clean up your own version of adapter.js https://chromium.googlesource.com/chromium/src.git/+/lkgr/chrome/test/data/webrtc/adapter.js first and see how many tests break.

I hope it won't be many but if there are those probably use videoElement.src instead of srcObject.

Whats the latest here?

still blocked on adapter. Lets do the breaking change there next and bump the major version?

According to chromestatus.com metrics, the promise-based version of getUserMedia is used ~3.5 times more than the prefixed version.
Still too much usage of the prefixed version to remove, but maybe low enough to initiate deprecation.

The issue I mentioned in #8 is now https://github.com/webrtcHacks/adapter/issues/712, and https://github.com/webrtcHacks/adapter/issues/764 is also relevant.