notifying the site of a browser intervention can be user harming

[pes10k]

This review is part of the requested PING review.

In some cases, when the browser mutes or rejects an effort from the page to autoplay media, it will be against the user's interests to notify the page (the whole reason the browser rejected the autoplay request in the first place is because the browser didn't think the page was acting in the user's best interests). For example, if the browser rejects an <audio>'s autoplay request bc the browser thinks in an invasive ad, and the page is notified of that intervention and responds with a different, non-autoplaying invasive ad, this proposal would leave users worse off.

The spec should talk through these tradeoffs, so that implementors can benefit from the group's expertise and (as best as possible) ensure that this feature does not end up working against users.

[KevinD313]

If they are isolated from the outside and try different ways to connect then it’s harmful to their pride