[BUG] Exclusionary rules to the Injection blacklist settings are ignored

Open
#69 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
tooling

Research direction

Reproduce the reported blacklist setup with a local WebM file and the linked userscript in Firefox. Inspect the blacklist and exclusion-matching entry points; done means an exclusion rule allows the userscript on matching WebM URLs while the broader file:// blacklist still blocks other URLs.

Written by the indexing model from the issue text.

Description

Sequence of actions:
  1. Set the following Injection blacklists under the Blacklist settings:
file://*/*
@exclude-match file://*/*.webm
  1. Install the following userscript:
https://github.com/WhatIsThisImNotGoodWithComputers/webm-looper-userscript/raw/master/webm-looper.user.js
  1. Open a local WebM file in the browser (e.g., file:///home/user/Downloads/sample.webm).
Problem:

Our userscript fails to execute indicating that our exclusionary rule was ignored. When clicking the greyed out Violentmonkey extension icon on the page that our WebM is playing in, the following message is displayed:

Blacklisted in Violentmonkey's settings
file://*/*

I tried these other following exclusionary rules which produced the same result:

@exclude file://*/*.webm
@exclude-match *://*/*.webm
@exclude *://*/*.webm
Expected result:

Our userscript should execute due to the inclusion of the @exclude-match rule.

Devtools console contents:
Environment:
  • OS: Debian GNU/Linux 12 (bookworm) x86_64
  • Browser: Mozilla Firefox 142.0 (64-bit)
  • Violentmonkey Version: 2.31.0
Dominant language
MDX
Stars
55
Forks
35
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from violentmonkey/violentmonkey.github.io

All issues in violentmonkey/violentmonkey.github.io

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.