[TPAC 2018] Autoplay Policy Informal Meeting Notes about autoplay HOT 11 CLOSED

Because it's not mentioned above, I believe that document.autoplaPolicy should look like this:

partial interface Document {
  readonly attribute Promise<AutoplayPolicy> autoplayPolicy;
};

from autoplay.

Is there any precedent for a readonly attribute Promise? It seems really weird to have a resolved Promise for a value that can change over time.

from autoplay.

from autoplay.

Is there any precedent for a readonly attribute Promise? It seems really weird to have a resolved Promise for a value that can change over time.

Will spin this off into issue 6.

from autoplay.

Can this have also an explicit permission request like notifications?

    if (Notification.permission === "granted") {
      console.log("We have notification permission");
      return;
    }
    Notification.requestPermission();

At the moment, the way autoplay blocking is implemented is breaking VoIP applications that are waiting for somebody to call and only then ring the sounds (w/o user interaction).

from autoplay.

from autoplay.

What I meant is that it doesn't have to be accessible ONLY through permissions.

At the moment, there are multiple mechanisms that disable the behaviour: https://sites.google.com/a/chromium.org/dev/audio-video/autoplay

Adding additional exception, when "audioapi" permission is granted would work perfectly. This way chat/voip developers will be able to request relevant permissions upon the start of the application, and it won't change the flow for the others.

from autoplay.

I think the WebRTC use case is separate and distinct from the annoying cases that browsers are mostly trying to block, and is probably only blocked because it passes through the same top level API surface; HTMLMediaElement.play().

Firefox allows sites which have been granted persistent camera and microphone permissions to autoplay, in order to permit cases like you're describing. Our opinion was that since the browser explicitly prompts the user for permission for the site to access the camera/microphone before a WebRTC stream plays, the user has clearly signaled intent to allow media on that site. Maybe you should file bugs with the other browsers asking them to implement the same exception?

from autoplay.

Chrome and Safari both allow autoplay while a page is using getUserMedia. It seemed a bit better than only relying on the permission.

from autoplay.

Would appreciate a heads-up when a specification is available for this, as this falls into my bailiwick docs-wise.

from autoplay.

Close this issue because this is just for some old discussion, and we already started editing a specification for Autoplay Detection API.

from autoplay.