- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Nov 2023 09:46:24 +0000
- To: public-webrtc-logs@w3.org
> "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..." I don't think it's a common user journey to click on some [screen-share] button in the Web app, **close the lid**, carry the laptop over to another room, then open the lid and expect to answer the screen-share dialog then. In fact, I expect most Web applications will also end up **disconnecting from the meeting** when you try that. Further, if you already interact with the dialog to stop the capture, closing the lid will stop the capture. I think dismissing the dialog in the same case will be more expected. > Users close the screen. They open it later and expect to see what was there before, just like a book. Books don't have dangerous side effects (unless one lives on Discworld). Before we execute a dangerous action on behalf of the user, we double-check the user's true intention through an intentionally-frictive prompt. Whatever tests we run to ensure we execute the user's true wishes, I believe these tests should be executed together, and never a day or two apart. > The laptop doesn't say Would having a dedicated error help the applications communicate to the user what went wrong? (It doesn't seem necessary to me, but if it helps others, I'm glad to support it.) > I don't think we should make assumptions about what the user wants or doesn't want. Not making the proposed change is itself an assumption-driven choice. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/287#issuecomment-1825402463 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 November 2023 09:46:26 UTC