Re: Screensharing - Application restricting whole screen

Den 25. nov. 2015 21:07, skrev Martin Thomson:
> On 25 November 2015 at 06:29, Eric Rescorla <ekr@rtfm.com> wrote:
>> It's about making it harder for them unintentionally to do so.
> 
> So what is wrong with being able to check after the fact?
> 
> I have to say, this seems a lot like security shibboleth.  You are
> right, that this sort of thing only prevents accidents, but correcting
> a mistake and preventing it are much the same here.  I expect that the
> browser will offer warnings in the case that you choose to select an
> entire monitor anyway.
> 

Thinking about this from an app developers' perspective...

if I have an app that is chiefly useful when sharing the whole screen,
I'll want to have my users work past a minimum of confusing dialogs when
getting the right thing to happen. So I'll want a constraint that says
"only ask for the whole screen", so that the user can answer yes/no
rather than have a dozen choices, most of which don't work right.

(remote assistance apps come to mind)

If I have an app that could work with either windows or screens, I'm
going to be envious of the simplicity of my colleague's screen-only app
and want the same kind of dialog. So I may go to screen-only too, if the
first one can.

Conclusion: Constraints that select screen-only are tempting, and may be
inevitable (in the sense that devs will add them whether we like them to
or not).
The presence of only that kind of constraint may cause more people to do
whole-screen sharing when they could have done window sharing, which is
not a Good Thing.

I am not clear on what conclusions I draw from that in "what the spec
should say".

Received on Thursday, 26 November 2015 07:41:54 UTC