Re: [mediacapture-screen-share] Should pending getDisplayMedia() calls reject on sleep and/or screen-lock? (#287)

> I think the UA should do something special here, not the application.

The user often doesn't know or care about the difference.  They tell their computer to do a thing.  They expect the computer to do the thing they told it to do.  Permission prompts are already a source of friction.  ("I told it to use my webcam, why is it now asking me if I'll allow it to use my webcam?")  With your proposal, there will be additional friction.  ("I started setting up for the meeting at my desk.  Now I closed my laptop, carried it to the conference room, and it says that I rejected permission?  I did no such thing...")

Please consider the way users see these things in the total presentation to them.  The layers aren't always apparent to the users.

>Rationale to reject:
>
> - A user closing a laptop lead with an outstanding prompt to start X, might expect their action to implicitly reject X.

I can't think of any other action the user would expect the laptop to give up on just because the user closed the laptop.  Users close the screen.  They open it later and expect to see what was there before, just like a book.  They don't need to know or care about the hundreds of things that happen with all the various levels of power states to keep their data and apps ready-to-go.

The laptop doesn't say, "you closed me, so I guess you don't need this Word document anymore."  It doesn't say, "I guess the calculator you opened and didn't type anything into is no longer needed."  It makes no assumptions at all.

Without some insurmountable technical reason, or an well-established well-known user story backed by some at-least minimal UX research, I don't think we should make assumptions about what the user wants or doesn't want.  Let's leave the prompt and let the user decide.

-- 
GitHub Notification of comment by bradisbell
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/287#issuecomment-1824837456 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 23 November 2023 19:16:53 UTC