[Chromium] Remove auto-play switch from settings

[javifernandez]

Configuration

Wolvic version: 1.2
Wolvic build ID:

Hardware: ML2

Steps to Reproduce

1. Go to Settings > Display
2. Enable the auto-play feature
3. Go to a web-size offering videos (eg, YouTube)
4. Select one of the available videos

Current Behavior

The video doersn't play unless the user clicks on the "play" button

Expected Behavior

The video should be played as soon as the web-size is loaded

Possible Solution

Context

Error Logs and Stack Traces

[svillar]

This is not really a bug. That feature affects the HTML5 video autoplay feature. In the case of YouTube they use their own player (<ytd-player> tag) which is not really affected by that setting, YouTube player has its own autoplay setting

[javifernandez]

I'm not sure about how this issue has been closed. I have verified that when using the Gecko backend, it s the YouTube site the one controlling the auto-play feature. However, when using the Chromium 1.8 backend, the auto-play doesn't work even if enabling in in the TY player interface.

[svillar]

As commented offline auto-play in chromium browsers works diferently https://developer.chrome.com/blog/autoplay

After I played a YT video once, I relaunched Wolvic and auto-play worked

[javifernandez]

As commented offline auto-play in chromium browsers works diferently https://developer.chrome.com/blog/autoplay

After I played a YT video once, I relaunched Wolvic and auto-play worked

I can confirm the mentioned behavior. However, then the issue is that the 'auto-play' switch in the Privacy and Security settings dialog doesn't makes sense when using the Chromium backend.

[svillar]

As commented offline auto-play in chromium browsers works diferently https://developer.chrome.com/blog/autoplay
After I played a YT video once, I relaunched Wolvic and auto-play worked

I can confirm the mentioned behavior. However, then the issue is that the 'auto-play' switch in the Privacy and Security settings dialog doesn't makes sense when using the Chromium backend.

OK let's rename the bug then. After all this is a mere UI issue then