Firefox does not support browser tab Capture
Categories
(Core :: WebRTC, defect)
Tracking
()
People
(Reporter: mikegorney, Unassigned)
Details
Steps to reproduce:
call getDisplayMedia() in javascript.
Actual results:
Firefox prompts the user to select from the display surfaces "Window" or "Screen".
Expected results:
The spec (https://www.w3.org/TR/screen-capture/#dfn-display-surface) says that "the user agent MUST still offer the user unlimited choice of any display surface."
The spec provides for 3 surfaces: Monitor, Window, and Browser, and a third option should have been provided.
I also think Firefox should narrow the stream capture down to the HTML contents (like Chrome/Edge) when a specific tab is chosen. There is no reason for the toolbar, bookmarks, extensions, or any other additional UI elements to be exposed.
|
||
Comment 2•2 years ago
|
||
Setting this to Core > WebRTC, if this is not the right component, please move it to a more appropriate one. Thanks!
|
||
Comment 3•2 years ago
|
||
This is a request for browser tab capture, so duping it on that. FWIW we do support it behind a pref if you go to about:config and set media.getusermedia.browser.enabled to true, but our UX picker isn't great if you have a lot of tabs.
I'm renaming the issue from "Firefox does not conform to the Screen Capture spec", because the spec doesn't mandate the pool of available choices, only that JS must not be able to narrow the pool. So Firefox is technically compliant.
The spec (https://www.w3.org/TR/screen-capture/#dfn-display-surface) says that "the user agent MUST still offer the user unlimited choice of any display surface."
That language was added in w3c/mediacapture-screen-share#186 and pertains to "The user agent MAY use the presence of the displaySurface constraint and its value to influence the presentation to the user of the sources to pick from." — it means any "available" surface, as it says in the paragraph preceeding it.
But none of that changes that enabling tab capture is a priority and on our roadmap. It's just by user demand, not the spec. I hope we have it soon!
Description
•