- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Oct 2024 22:37:56 +0000
- To: public-webrtc-logs@w3.org
> ... Controls belong directly in the Web application. Our user studies show quite poor discoverability for anything outside of the viewport. Is that bad news for the other capture-related controls in the chrome bar, plus Captured Surface Switching? > For a real use example directly from a professional app, see this instead: Thanks! I agree looking at real apps is helpful. But how is this placement superior? <img width="1003" alt="image" src="https://github.com/user-attachments/assets/432e490c-fbba-4a3b-b31c-b4417727f4a2"> It's obscuring what I'm sharing. Isn't it better here? <img width="982" alt="image" src="https://github.com/user-attachments/assets/03bdf77c-a723-4ee2-9d85-c162575705aa"> Here it would work (the same) in every VC app instantly, not just Meet, without permission or opt-in, without scaring anyone. Did the user studies consider whether the consistent placement across all VC apps aided discoverability? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/13#issuecomment-2423331165 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 October 2024 22:37:57 UTC