- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Sep 2021 12:55:51 +0000
- To: public-webrtc-logs@w3.org
> This PR restores spec-mandated behavior that was lost by mistake Could you please clarify what was lost and why it should be restored? Reading #132 does not make it as obvious to me. Both the pre-PR and post-PR texts discuss rejecting getDisplayMedia() if called without user-interaction. The post-PR text lets the UA allow gDM in the split second right after the user interacts with the page (it's unclear to me what the pre-PR text specifies here). Is this really a problem? > making [crbug 920733](https://bugs.chromium.org/p/chromium/issues/detail?id=920733) a spec violation again Isn't the requirement for transient activation sufficient here? (Modulo the aforementioned timing issue.) > Feel free to open a new issue, but note there's no precedent for specs mandating intrusiveness of prompts, and such a spec would likely be anything but short. I think it would be useful to at least say that the dialog shown to the user may not steal away focus/activation from anything other than the current browsing context. The user can always alt+tab to another native app while the UA is still processing the already-approved call to `getDisplayMedia`, and that this would result in the alt+tab being undone is unfortunate and preventable. I don't think #192 prevents that (due to timing issues), so would be good to generally say that the browser should employ prompts and dialogs that do not risk introducing such issues at the edges. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/pull/192#issuecomment-922901296 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 September 2021 12:55:53 UTC