Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/uBlockOrigin/uBlock-issues/issues/760 below:

Implement `$queryprune` parameter · Issue #760 · uBlockOrigin/uBlock-issues · GitHub

• I verified that this is not a filter issue
  • Filter issues MUST be reported at filter issue tracker
• This is not a support issue or a question
  • Support issues and questions are handled at /r/uBlockOrigin
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue
  • Your issue may already be reported.
• I tried to reproduce the issue when...
  • uBlock Origin is the only extension
  • uBlock Origin with default lists/settings
  • using a new, unmodified browser profile
• I am running the latest version of uBlock Origin
• I checked the documentation to understand that the issue I report is not a normal behavior

In #46 about $rewrite parameter author said:

I won't implementing this filter option, I see too many issues with it. I am however open to implement a different filter option with similar purpose, but which would not suffer the issues I see with how rewrite has been designed.
...
I see a better way to implement similar option but with a more focused purpose: to remove specific query parameters from a URL:

||content.uplynk.com/ext/.m3u8?$querystrip=

Where the querystrip option would mean: "remove all query parameters matching the given lists of tokens or pattern".

Will the $querystrip parameter be realized?

[A specific URL is MANDATORY for issue happening on a web page, even if it happens "everywhere"]

1. [First Step]
2. [Second Step]
3. [and so on...]

[What you expected to happen]

[What actually happened]

• uBlock Origin version:
• Browser Name and version:
• Operating System and version:

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4