-
Notifications
You must be signed in to change notification settings - Fork 470
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
Twitch's new nag screen #319
Comments
Ok you can ZAP IT . Click the UBLOCK icon and there should be a lighting bolt. click it and then put mouse over the Video player and it will remove it. Edit. finding out it works on one streamer. So if it comes up again you zap it. Trying it figure out what to block once i find it or figure something out ill LET YOU KNO |
Here is what's displayed without fixing it with uBlock element picker Using element picker on the blank space above the video I get this element to block, and click create. Now there is no popup after 30+ min on multiple streams, whereas it popped up every few minutes before. Here is the line it adds in "My filters" in the uBlock settings: You may be able to copy the same filter it created for my instance into your filters page to see if that blocks the popup for you. Otherwise, create the filter yourself using element picker as I did above. |
Zapping is temporary, so it's best to use the element picker to make a permanent filter, which you can remove any time by deleting the line you create in the uBlock "My filters" page. See my comment above for the line I added to it. |
I added that line into my filter list and im still getting the nagware further invetigation may be needed. |
@Xelor41023 And you have "Enable my custom filters" checked? If so, when you get the popup next time, use the uBlock element picker and select the empty space just outside the top of the video within the player so that the correct element is picked like where I have the + sign in the image below. Maybe the line I suggested isn't universal and yours may look different? |
I used this CSS Customization instead:
|
They are doing this now.
The text was updated successfully, but these errors were encountered: