They're permission identifiers for camera, microphone, screen-sharing and various forms of screen-sharing we used to support (and still have code for sorta in some cases behind prefs). While there's no way to persist GRANTS for screen sharing (the spec forbids it), users can BLOCK it. Their organization is perhaps unfortunate, outdated, based on the non-spec `mediaSource` constraint we hope to deprecate in bug 1557174. getUserMedia API wise: - We no longer support application sharing. - Screen == window now (bug 1474376, I believe "screen" is used internally) - Browser is tab sharing we never built UX for (from Firefox Hello days. May still work behind pref, modulo there being no UX) - audiocapture is the audio equivalent of tab sharing (also behind pref) - other is nothing. Our internal permission code however may still be organized this way.
Bug 1533575 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
They're permission identifiers for camera, microphone, screen-sharing and various forms of screen-sharing we used to support (and still have code for sorta in some cases behind prefs). While there's no way to persist GRANTS for screen sharing (the spec forbids it), users can persist BLOCKs. Their organization is perhaps unfortunate, outdated, based on the non-spec `mediaSource` constraint we hope to deprecate in bug 1557174. getUserMedia API wise: - We no longer support application sharing. - Screen == window now (bug 1474376, I believe "screen" is used internally) - Browser is tab sharing we never built UX for (from Firefox Hello days. May still work behind pref, modulo there being no UX) - audiocapture is the audio equivalent of tab sharing (also behind pref) - other is nothing. Our internal permission code however may still be organized this way.