Bugzilla

Sorry, I still need to close this bug. If you really need to click-to-play mode then you can change your setting to do that, see details [here](https://docs.google.com/document/d/1p81bYntlLMTxXoANnQXS9KH0TZ4y8aKKeH9x3GVS3eY/edit#heading=h.fphxgnr2pwqf).||

So for autoplay, I agree that the ideal situation should be `click-to-play` that only plays the media when users do action on it (eg. click). However, that requires to propagate a flag to the element in order to know if the play invocation is really triggered by users. However, the spec of that flag propagation has some long existing defect and finally all vendors agreed to abandon that and use a new spec instead, which is [`sticky/transient` user activation](https://html.spec.whatwg.org/multipage/interaction.html#user-activation-data-model). 

Currently Firefox uses `sticky` as the default policy for blocking autoplay, and also provide the option of switching to `transient` activation and the oldest implementation (`click-to-play`). The reason we don't use `click-to-play` as a default option is because it exists some spec issue, and won't work for every sites. (Some sites would be never allowed to start playing because the flag propagation failed) And `transient` activation also didn't work for every sites, because each website has different response time to play media. 

Anyway, you can change your blocking autoplay to different policy by modifying the pref. And the `click-to-play` is the one you're looking for, which is also the oldest blocking autoplay implementation on Firefox, but we don't guarantee that that policy works for every site.

Sorry, I still need to close this bug. If you really need to click-to-play mode then you can change your setting to do that, see details [here](https://docs.google.com/document/d/1p81bYntlLMTxXoANnQXS9KH0TZ4y8aKKeH9x3GVS3eY/edit#heading=h.fphxgnr2pwqf).

So for autoplay, I agree that the ideal situation should be `click-to-play` that only plays the media when users do action on it (eg. click). However, that requires to propagate a flag to the element in order to know if the play invocation is really triggered by users. However, the spec of that flag propagation has some long existing defect and finally all vendors agreed to abandon that and use a new spec instead, which is [`sticky/transient` user activation](https://html.spec.whatwg.org/multipage/interaction.html#user-activation-data-model). 

Currently Firefox uses `sticky` as the default policy for blocking autoplay, and also provide the option of switching to `transient` activation and the oldest implementation (`click-to-play`). The reason we don't use `click-to-play` as a default option is because it exists some spec issue, and won't work for every sites. (Some sites would be never allowed to start playing because the flag propagation failed) And `transient` activation also didn't work for every sites, because each website has different response time to play media. 

Anyway, you can change your blocking autoplay to different policy by modifying the pref. And the `click-to-play` is the one you're looking for, which is also the oldest blocking autoplay implementation on Firefox, but we don't guarantee that that policy works for every site.

Sorry, I still need to close this bug. If you really need to click-to-play mode then you can change your setting to do that, see details [here](https://docs.google.com/document/d/1p81bYntlLMTxXoANnQXS9KH0TZ4y8aKKeH9x3GVS3eY/edit#heading=h.fphxgnr2pwqf).

So for autoplay, I agree that the ideal situation should be `click-to-play` that only plays the media when users do action on it (eg. click). However, that requires to propagate a flag to the element in order to know if the play invocation is really triggered by users. However, the spec of that flag propagation has some long existing defects and finally all vendors agreed to abandon that and use a new spec instead, which is [`sticky/transient` user activation](https://html.spec.whatwg.org/multipage/interaction.html#user-activation-data-model). 

Currently Firefox uses `sticky` as the default policy for blocking autoplay, and also provide the option of switching to `transient` activation and the oldest implementation (`click-to-play`). The reason we don't use `click-to-play` as a default option is because it exists some spec issue, and won't work for every sites. (Some sites would be never allowed to start playing because the flag propagation failed) And `transient` activation also didn't work for every sites, because each website has different response time to play media. 

Anyway, you can change your blocking autoplay to different policy by modifying the pref. And the `click-to-play` is the one you're looking for, which is also the oldest blocking autoplay implementation on Firefox, but we don't guarantee that that policy works for every site.

Sorry, I still need to close this bug. If you really need to click-to-play mode then you can change your setting to do that, see details [here](https://docs.google.com/document/d/1p81bYntlLMTxXoANnQXS9KH0TZ4y8aKKeH9x3GVS3eY/edit#heading=h.fphxgnr2pwqf).

So for autoplay, I agree that the ideal situation should be `click-to-play` that only plays the media when users do action on it (eg. click). However, that requires to propagate a flag to the element in order to know if the play invocation is really triggered by users. However, the spec of that flag propagation has some long existing defects and finally all vendors agreed to abandon that and used a new spec instead, which is [`sticky/transient` user activation](https://html.spec.whatwg.org/multipage/interaction.html#user-activation-data-model). 

Currently Firefox uses `sticky` as the default policy for blocking autoplay, and also provide the option of switching to `transient` activation and the oldest implementation (`click-to-play`). The reason we don't use `click-to-play` as a default option is because it exists some spec issue, and won't work for every sites. (Some sites would be never allowed to start playing because the flag propagation failed) And `transient` activation also didn't work for every sites, because each website has different response time to play media. 

Anyway, you can change your blocking autoplay to different policy by modifying the pref. And the `click-to-play` is the one you're looking for, which is also the oldest blocking autoplay implementation on Firefox, but we don't guarantee that that policy works for every site.

Sorry, I still need to close this bug. If you really need to click-to-play mode then you can change your setting to do that, see details [here](https://docs.google.com/document/d/1p81bYntlLMTxXoANnQXS9KH0TZ4y8aKKeH9x3GVS3eY/edit#heading=h.fphxgnr2pwqf).

So for autoplay, I agree that the ideal situation should be `click-to-play` that only plays the media when users do action on it (eg. click). However, that requires to propagate a flag to the element in order to know if the play invocation is really triggered by users. However, the spec of that flag propagation has some long existing defects and finally all vendors agreed to abandon that and used a new spec instead, which is [`sticky/transient` user activation](https://html.spec.whatwg.org/multipage/interaction.html#user-activation-data-model). 

Currently Firefox uses `sticky` as the default policy for blocking autoplay, and also provides the option of switching to `transient` activation and the oldest implementation (`click-to-play`). The reason we don't use `click-to-play` as a default option is because it exists some spec issue, and won't work for every sites. (Some sites would be never allowed to start playing because the flag propagation failed) And `transient` activation also didn't work for every sites, because each website has different response time to play media. 

Anyway, you can change your blocking autoplay to different policy by modifying the pref. And the `click-to-play` is the one you're looking for, which is also the oldest blocking autoplay implementation on Firefox, but we don't guarantee that that policy works for every site.