-
Notifications
You must be signed in to change notification settings - Fork 847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firefox will be identified as "Not a supported browser." if mozGetUserMedia is removed #1156
Comments
From what I recall you agreed to this in the context of #151 -- it has been a while though. |
Thanks for the link. To clarify, I intimated "there are no plans to unprefix it." on |
If you want to do something more effective than breaking a ton of sites and reducing Firefox WebRTC reach further make that method throw but keep it around? |
https://developer.mozilla.org/en-US/docs/Web/API/RTCSessionDescription/RTCSessionDescription -- removing the callback variant here might prevent more adoption of navigator.getUserMedia (it is surprising that MDN has examples that do not even work in Firefox, no?) |
#764 identified problematic
detectBrowser
code which prevents browsers from removing non-standard APIs:E.g. Firefox cannot remove
mozGetUserMedia
without this returning "Not a supported browser."The #1146 fix to #764 is unsatisfactory, relying on an API that is not standards-track to solve this problem only for Chromium.
The core problem, that this function treats browsers without specific non-standard APIs as "Not a supported browser." remains unaddressed.
The text was updated successfully, but these errors were encountered: