Re: [mediacapture-screen-share] Revisit: Let getDisplayMedia() influence the default type choice in the picker (#184)

> I think my comment is polite and relevant.

The comment dismisses the 'reject screen' position as if there is no other ground than purity.
Let's focus on finding some common ground instead.

> Could you point to precedents where Apple or Mozilla have knowingly accepted spec-changes that would put them in violation of the spec

Sure, this happens all the time, for instance when renaming properties. In those cases, backward compatibility is what we look at to understand whether we can make that change and how we can do it. It is fine if, for a given period of transition, the implementation is not fully aligned with the spec as long as there is a practical path to match the spec that people want to follow.

AIUI, that is what you are doing here: identify backward compatibility issues and evaluate how to solve them.
Given there seems to be solutions that Chrome used successfully in the past (needs validation from your side), and given you expressed interest in fixing those issues, I am thinking we have a path forward.

Also, I do not think the PR would say that a UA MUST NOT select 'screen' as default surface (which would outlaw Chrome).
The PR would say that a web page can use a property to hint at selecting tab or window, not screen.
The PR would not prevent implementing another property that would enable/disable a legacy 'pick screen first' behavior.

GitHub Notification of comment by youennf
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 1 February 2022 13:24:30 UTC