- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Sep 2021 13:11:57 +0000
- To: public-webrtc-logs@w3.org
> The shim is careful not to await anything else, yet a microtask checkpoint is unavoidable It is avoidable by having the shim returning the native promise returned by getDisplayMedia. The only downside is that you cannot change the object being resolved, but you can update the object itself: add tracks, remove tracks... Looking at the HTML event loop, we can also see that after the micro task checkpoint, there are additional tasks that need to be done, some of which might trigger firing events. > These are two distinct preferences: > > 1. Global or per-surface. (Discussed in this section.) > 2. Attribute or method. (Discussed in the next section.) I was meaning a global attribute, somewhere in navigator. With the current focus API design, in particular the restriction to read the focus-or-not value synchronously in the task resolving the promise, I do not see a need to have a per-track method. Let's say the application wants a behavior for all getDisplayMedia calls. It will set the attribute once. 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 method is less intuitive to me. > one challenge with writable attributes is that Web-developers would not as readily expect setting of attributes to potentially raise an exception. I do not think the plan for setting this attribute is to raise an exception. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/190#issuecomment-927861004 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:11:59 UTC