Closed Bug 1247573 Opened 8 years ago Closed 6 years ago

Incorrect compat table content for Chrome

Categories

(Developer Documentation Graveyard :: API: Web Audio, defect, P5)

Product:
Developer Documentation Graveyard
Component:
API: Web Audio
Platform:
All
Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: monfera.robert, Unassigned)

References

(
URL
)

Details

:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: 

:: Details

Chrome 48 (on OS X at least) has MediaDevices.getUserMedia as undefined. The compat table of the page erroneously states that Chrome has this since Chrome 47.
https://webrtc.github.io/samples/src/content/devices/input-output/ works for in Chrome 48 (OS X) without activating the experimental flag, so it looks like it works…
Thanks Jean-Yves! I did't doubt that there is a way of capturing audio; there are lots of programs that do, including your link or the pen I'm working on. My report was that MediaDevices.getUserMedia is undefined in Chrome 48, whereas the doc suggests that it exists as of Chrome 47. Just start Chrome and type navigator.mediaDevices.getUserMedia and it'll return undefined. The example probably works due to the fact that it detects that it's undefined, and if so, it uses the legacy stuff that the page on navigator.getUserMedia says you should NOT use. So I still believe that the page is in error.
... I'll need to double-check why the linked example works despite navigator.mediaDevices.getUserMedia returning undefined in a new browser tab, as looking in the code, the promisifiedGUM isn't present.
... looks like adapters.js is shimming it? I don't think it would count as true support for MediaDevices.getUserMedia in Chrome 48. As adapters.js is a 2kLoC file I'd rather go the clean route of testing if navigator.MediaDevices.getUserMedia is even bound in a fresh browser tab, rather than what features are being present after loading a large compat layer. Or am I missing something?
The compat tables have been renewed. Please open issues against https://github.com/mdn/browser-compat-data if you still see issues with it.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.