Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • adblockplusui adblockplusui
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 247
    • Issues 247
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Adblock inc
  • Extensions
  • Adblock Plus
  • adblockplusuiadblockplusui
  • Issues
  • #1031
Closed
Open
Created Sep 23, 2021 by Thomas Greiner@ThomasGreinerOwner

Stop relying on content filtering functionality for previewing new filters

Background / User story

In https://gitlab.com/eyeo/webext/webext-sdk/-/issues/80 , we discussed whether the SDK should/can provide us with the ability to apply new filters to websites, which we're using for the Block element feature, when the user decides to the add the filters from the dialog. Comparing the various alternatives, the quickest approach to make up for the loss of that ability, is to reuse the existing filter preview functionality, which is a rough representation of the effects the filters will have on the page when they're applied.

There are some problems with this approach (see comment, #824, #1032), but those may only concern edge cases and can be resolved with a page reload. Nevertheless, we should adjust the Block element dialog UI accordingly, so that users don't have wrong expectations about what happens when adding the filters via that dialog - especially if they have made modifications to the suggested filters.

What to change

  • Design: https://www.figma.com/file/yVwNC6qDEpATL4m1VLQWDk/ABP-Bubble-UI?node-id=807%3A523
  • Spec: eyeo/specs/spec!389
  • Development: TBD

Hints for testers

Clicking on "Block & reload page" button should not enable the filter preview before reloading the page.

Hints for translators

Added "composer_block_reload" string.

Edited Feb 01, 2022 by Thomas Greiner
Assignee
Assign to
Time tracking