- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Sep 2021 13:32:40 +0000
- To: public-webrtc-logs@w3.org
> Let's say the application wants to select the behavior for each getDisplayMedia call, it will update the attribute value each time within the promise resolution callback. A Web-developer would have to have non-trivial understanding of the feature in order to become convinced that there'd be no carry-over effect of focusing the wrong surface. They might explain it to themselves as "only the last capture gets focus or not" - but then, why does it sometimes not seem to work? There is no exception raised when they set the new value too late (e.g. `await` on an yet-unresolved-Promise). With a method, there would be, and that exception would not be unexpected. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/190#issuecomment-927879701 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 September 2021 13:32:42 UTC