Make NotFoundError when prompt() is called and availability monitoring is not available optional about remote-playback

[mfoltzgoogle]

I believe this step is to handle when the user agent has disabled device discovery in a way that won't change over the lifetime of the call to prompt(), so the user agent would have no reason to show a dialog anyway. I don't think we handle this specifically on Chrome for desktop and always show the dialog.

[mounirlamouri]

My understanding of step 8 is that the user agent should reject immediately if it knows that the dialog will show no devices. However, the case you present is different because we need to show the dialog and do the discovery and then realize there is nothing.

Is my understanding correct?

[avayvod]

Yes, I'm thinking about the case when the background availability monitoring is not available and we have to show the dialog to start active device discovery. We could argue that there's no timeout in this case as user could turn on a device at any moment.

[mounirlamouri]

In the case you describe, prompt() would hang while the dialog is visible and the state will stay disconnected which is all fine, right? If the user picks a device, it would switch the state to connecting and resolve the promise. Otherwise, it would reject the promise with NotAllowedError, right?

[avayvod]

Ok, one can argue that in the use case I describe above the UA doesn't know if the "list of available remote playback devices..." "...will remain so [empty] before the request for user permission is completed" which makes the step a no-op.