Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block autoplay on whitelisted site doesn't work #3138

Open
srirambv opened this issue Jan 29, 2019 · 11 comments
Open

Block autoplay on whitelisted site doesn't work #3138

srirambv opened this issue Jan 29, 2019 · 11 comments
Labels
bug feature/autoplay priority/P3 The next thing for us to work on. It'll ride the trains. QA/Yes release-notes/include

Comments

@srirambv
Copy link
Contributor

Description

Attempting to block autoplay on a site that is whitelisted is quite difficult than it sounds. On YT, changing autoplay to block only blocks on that video and not at domain level. The entry for a domain in brave://settings/content/autoplay doesn't result in blocking autoplay and user still needs to block it on each individual page

Steps to Reproduce

  1. Clean profile and visit YT
  2. Click site settings and change autoplay to Block
  3. Page asks for reload, reload the page and still plays the video
  4. Add https://youtube.com:443 entry in brave://settings/content/autoplay under block
  5. Open a new tab and load a YT video, still not blocked continues to autoplay
  6. Click on the site setting and change auto play setting, page reload triggers block
  7. Go back to YT home page and load another video this time autoplay block fails and video continues to autoplay

Actual result:

Watch the full steps here https://youtu.be/rAxzyo4-J_s

Expected result:

Adding a site exception should block autoplay at the domain level even if its added to whitelist

Reproduces how often:

Easy

Brave version (brave://version info)

Brave 0.59.31 Chromium: 72.0.3626.71 (Official Build) (64-bit)
Revision f52ccad2a6a3c65fc9e0c591a517ceab1198dac0-refs/branch-heads/3626@{#763}
OS All

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds?
    Yes

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields?
    N/A
  • Is the issue reproducible on the latest version of Chrome?
    N/A

Additional Information

Issue reported and discussed on https://community.brave.com/t/autoplay-was-blocked-on-this-page-not-actually-blocking-autoplay/33565/8
cc: @bbondy @brave/legacy_qa

@srirambv srirambv added this to the 1.x Backlog milestone Jan 29, 2019
@rebron rebron added the priority/P3 The next thing for us to work on. It'll ride the trains. label Jan 29, 2019
@rebron rebron removed this from the 1.x Backlog milestone Feb 7, 2019
@btlechowski
Copy link

@Brave-Matt
Copy link

@Brave-Matt
Copy link

@Brave-Matt
Copy link

@srirambv
Copy link
Contributor Author

This is still a problem. Unable to set YT to block autoplay since its whitelisted.

yt

cc: @bbondy @rebron this is regressed and needs to be fixed. Please assign a priority for this

@Zoooook
Copy link

Zoooook commented Sep 6, 2019

I'm not familiar with how Brave is architected, but wouldn't a simpler and more transparent solution be to pre-populate the user's Autoplay Allow list at chrome://settings/content/autoplay so that they have access to it, rather than having to code around a hidden whitelist?

@srirambv
Copy link
Contributor Author

srirambv commented Oct 6, 2019

+1 from @triolan1 via #6325

@srirambv
Copy link
Contributor Author

srirambv commented Jan 2, 2020

+1 from @stortzm via #7563

@rebron
Copy link
Collaborator

rebron commented Mar 24, 2020

@pilgrim-brave @pes10k Adding youtube to the block list still doesn't seem to block autoplay. Any ideas?

@rebron
Copy link
Collaborator

rebron commented Apr 28, 2020

@srirambv This should work now due to #8408

@posita
Copy link

posita commented Sep 29, 2020

+1 from me. I've tested both of these, and they cure the problem:

I'm unable to find sources for either of those, however.

@rebron rebron moved this to P3 backlog in Settings May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug feature/autoplay priority/P3 The next thing for us to work on. It'll ride the trains. QA/Yes release-notes/include
Projects
Status: P3 backlog
Development

No branches or pull requests

6 participants