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

blog.livedoor.jp #142763

Closed
adguard-bot opened this issue Feb 13, 2023 · 1 comment
Closed

blog.livedoor.jp #142763

adguard-bot opened this issue Feb 13, 2023 · 1 comment

Comments

@adguard-bot
Copy link

Issue URL (Annoyance)

http://blog.livedoor.jp/fightersmatome/archives/60197757.html

Comment

I understand that you all have made the decision not to hide these buttons in the past. However, in reality these buttons are annoying. The reason is that the buttons are always on the screen, even though there is already a button at the end of the article that has a similar function. Could you please reconsider whether you can use an annoyance filter to deal with this problem?

Screenshots

Screenshot 1

Screenshot 1

Screenshot 2

Screenshot 2

System configuration

Information value
Platform: Android 12
AdGuard product: AdGuard for Android v3.6.11+(54)
Browser: Chrome
AdGuard mode: VPN
Filtering quality: High-quality
HTTPS filtering: enabled
Stealth mode: disabled
DNS filtering: disabled
Filters: Ad Blocking:
AdGuard Base,
AdGuard Mobile Ads

Privacy:
AdGuard Tracking Protection

Social Widgets:
AdGuard Social Media

Annoyances:
AdGuard Annoyances

Language-specific:
AdGuard Japanese
Userscripts: disabled
@AdamWr
Copy link
Member

AdamWr commented Feb 13, 2023

These buttons are part of the website's functionality and only appear when website is scrolled up, so I'm not sure if it should be blocked.

Please add this rule:

blog.livedoor.jp###ld-floating-menu

to user rules.

#93604 (comment)

@AdamWr AdamWr closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2023
@AdamWr AdamWr removed the A: In progress Work on the issue is in progress label Feb 13, 2023
AdamWr added a commit that referenced this issue Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants