Opened 3 years ago

Last modified 10 months ago

#3749 new change

Encourage user to update subscriptions if there is at least one one day old subscription and user attempts to report an issue

Reported by: Lain_13 Assignee:
Priority: Unknown Milestone:
Module: User-Interface Keywords:
Cc: kzar, jeen, sebastian, athornburgh, greiner, saroyanm Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by greiner)

Environment

Firefox browser on PC and Mac

How to reproduce

0 (pre-requisite) There should be at least one 1 day old subscription (except AWRL and acceptable ads).

  1. Open any site.
  2. Select "Report issue on this page..."
  3. Select first or second option there and click "Next >".

Observed behaviour

If there are not too many subscriptions you will be able to report an issue normally.

Expected behaviour

If there are not too many subscriptions ABP should offer to update all lists and reload a page to check if this issue were already fixed.

Further information

See https://gitlab.com/eyeo/adblockplus/adblockplusui/issues/19

Change History (8)

comment:1 Changed 3 years ago by Lain_13

Since recently we got a lot of reports from users regarding unblocked ads on VK.com because their ads were added into whitelist. It's way too painful to answer each one to update their filters and check if they want to keep acceptable ads enabled or disable them.

Last edited 3 years ago by Lain_13 (previous) (diff)

comment:2 Changed 17 months ago by kzar

  • Cc kzar jeen sebastian athornburgh added
  • Component changed from Unknown to Platform
  • Platform changed from Firefox to Unknown / Cross platform

Seems like a sensible suggestion, if the user is reporting a problem why not first update their subscriptions and ask them to retry if they're out of date?

comment:3 Changed 17 months ago by kzar

  • Cc greiner saroyanm added
  • Component changed from Platform to User-Interface

(Sorry, just realised this probably comes under UI instead of Platform.)

comment:4 Changed 17 months ago by greiner

Sounds reasonable. What's the reason for ignoring the two filter lists you mentioned in step (0) during that check?

comment:5 follow-up: Changed 17 months ago by Lain_13

As I understand both have nothing to do with blocking ads and shouldn't cause false positives. I might be wrong about AWRL, though.

comment:6 in reply to: ↑ 5 Changed 17 months ago by greiner

Replying to Lain_13:

As I understand both have nothing to do with blocking ads and shouldn't cause false positives. I might be wrong about AWRL, though.

It's true that they're not directly related to blocking ads. That being said, I'd imagine that users could encounter problems with seeing too many/few ads if one of those two is out-of-date due to bad filters or recent website changes.

Admittedly, it might bit less likely that issues are caused by those so we may want to deprioritize them somehow in that process.

comment:7 Changed 17 months ago by greiner

I've created a spec issue for it at https://gitlab.com/eyeo/spec/issues/131

comment:8 Changed 10 months ago by greiner

  • Description modified (diff)
Note: See TracTickets for help on using tickets.