[Privacy] Request to disable monitoring when disableRemotePlayback is set about remote-playback

[avayvod]

Given there might be user agent specific UI (default controls or toolbar) depending on the monitoring, I don't think we can require the UA to stop all monitoring when the set of availability callbacks is empty.
It's similar for the disableRemotePlayback attribute. There might be other media elements loaded on some page or other browser feature depending on the monitoring (like tab casting).
The information is not exposed to the page via the specific element if its availability callbacks set is empty and/or if it has disableRemotePlayback set.

[mfoltzgoogle]

If disableRemotePlayback is set on a media element, won't that also disable remote playback UI on the default controls/toolbar?

I agree that an empty set of availability callbacks shouldn't disable monitoring though.

We may want to clarify that there if there is a browser level control to disable background monitoring, how the API should behave.

[avayvod]

Definitely not on the user agent's toolbar as it's unlikely refers to one single element.

disableRemotePlayback is to prevent remote playback of a certain media element, not availability monitoring although it does disable the media element specific availability related methods for consistency.

I'm not sure clarifying how browser features / settings affect the API is necessary as long as it affects it in a non-website breaking way like reporting no devices available and being consistent with it.

[mfoltzgoogle]

On re-reading, this issue will be closed by implementing the changes proposed in Issue #84.

The original suggestion is not correctly formed as discussed here; disableRemotePlayback applies to a single media element, not to background monitoring as a whole or any browser level controls that might require it.

I'm closing this, any further discussion of API behavior can continue in #84 or the forthcoming PR.